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.
building the graph…
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.Multi-token collectionAt least one ERC-1155 TransferSingle/TransferBatch and non-empty runtime code. 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.
GraphProjections of platform-prepared data for this entity; each tab is one projection (Ledger, Semantic, …)
Token flow: 101 addresses · latest 100 transfersLedger window only — addresses that moved this token in its latest transfers. The token itself sits in the centre and is not a party to them.
Transfers are backed by on-chain state changes.Derived unambiguously from chain data: this token's Transfer events are backed by matching state changes in the issuer's storage.
Structural relationships — deployer, implementation, same-bytecode, protocol.Interpreted actions (swap, supply, bridge) — arrives with the operations vitrine.Recurring on-chain patterns over time (analytics layer).Token transfers around this entity — who moved which assets, and with whom.EVM execution graph — the contract call tree.
0 nodes / 0 edgesidentity & risk as of today, not the windowOur timestamps say when the source reported this, not when it became true — so a quiet window cannot tell you what the verdict was at the time.