OverviewWhat this address is, since when, and how it is doing.ActivityEverything that happened here — transactions, transfers, internal calls, state changes.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.HoldersWho holds this asset now, ranked by balance.PoolsDEX pools this asset trades in, and its recent volume.GraphMoney flow and structure around this address.
TransactionsTransactions where this address is the sender or the recipient.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.DEX TradesSwaps where this address is the trader, across DEX protocols.
OndoONDO
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.Fungible tokenAn ERC-20 surface on the code that actually executes (decimals, symbol, name, totalSupply), at least one observed ERC-20 Transfer, and zero ERC-721/1155 events. Says what the interface is — not whether the token is legitimate. Derived unambiguously from chain data.Transfers state-backedThis token's Transfer events are backed by matching state changes in the issuer's storage. Derived unambiguously from chain data.
High traffic→Very high transaction volume (≥ 100,000 txns).