OverviewWhat this address is, since when, and how it is doing.ActivityEverything that happened here — transactions, transfers, internal calls, state and storage changes, emitted events.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, …)
Value moved around this entity — token and ETH transfers, with whom and how much.Interpreted actions (swap, supply, bridge) — arrives with the operations vitrine.Structural relationships — deployer, implementation, same-bytecode, protocol.Recurring on-chain patterns over time (analytics layer).A single user intent across an ERC-4337 UserOp.
Ledger: 9 counterpartiesLedger window only — unique counterparties in the latest transfers; the all-time aggregate is on its way from the data platform · 28 movements in 21 transactions · 28 ETH, 0 token · over 2d
loading graph engine…
0 nodes / 0 edgesgesturestap = panel · 2×tap = expand/collapse · shift+tap = hide · →/← expand/collapse levelidentity & 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.