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.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.
GraphProjections of platform-prepared data for this entity; each tab is one projection (Ledger, Semantic, …)
Ledger: 99 counterparties · latest 824 transfersLedger window only — unique counterparties in the latest transfers; the all-time aggregate is on its way from the data platform
Structural relationships — deployer, implementation, same-bytecode, protocol.Token transfers around this entity — who moved which assets, and with whom.Interpreted actions (swap, supply, bridge) — arrives with the operations vitrine.EVM execution graph — the contract call tree.Recurring on-chain patterns over time (analytics layer).A single user intent across an ERC-4337 UserOp.
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.