OverviewWhat this address is, since when, and how it is doing.TransactionsTransactions of this address and everything inside them — transfers, internal calls, state and storage changes, emitted events, DEX trades.WithdrawalsBeacon-chain validator withdrawals credited to this address — paid by the consensus layer, with no transaction behind them.GraphMoney flow and structure around this address.
Token TransfersFungible token transfers — ERC-20, plus ERC-777 and ERC-4626 behind the chips.·NFT TransfersERC-721 and ERC-1155 transfers. Each row names one token id; ERC-1155 also says how many copies moved.·InternalInternal transfers — value-carrying contract calls (CALL / DELEGATECALL / SELFDESTRUCT).·State ChangesBlocks where this address's own account state changed — balance, nonce, code.·StorageContract storage activity: slots written, who writes them, how deep the calls go.·EventsThe event log this contract itself emitted, decoded where the ABI is known.·DEX TradesSwaps where this address is the trader, across DEX protocols.
ContractThe address currently carries runtime code. Derived unambiguously from chain data.Had runtime codeRuntime code existed at this address at some point of its history. Derived unambiguously from chain data.
Tx HashThe transaction this transfer happened inside — an internal transfer has no hash of its own.
Time
Type
CounterpartyThe other side of this transfer — who paid this address, or who it paid. Often not a party to the transaction at all.
In transactionThe transaction this transfer ran inside: who sent it, and what it was aimed at. This address is usually neither — the value arrived while somebody else's operation was executing.