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.
building the graph…
#25,928,610The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 17,021,037 — the earliest block among the facts that earned it.Code deployed onceThe contract carries code, and that code was placed here once — never removed and re-created. Derived unambiguously from chain data. Known from block 17,021,037 — the earliest block among the facts that earned it.No owner, immutable codeNo Ownable owner was ever set and the code cannot be replaced — there is no control surface to hold. Derived unambiguously from chain data. Known from block 17,021,037 — the earliest block among the facts that earned it.
GraphProjections of platform-prepared data for this entity; each tab is one projection (Ledger, Semantic, …)
Structural relationships — deployer, implementation, same-bytecode, protocol.Value moved around this entity — token and ETH transfers, with whom and how much.Interpreted actions (swap, supply, bridge) — arrives with the operations vitrine.Recurring on-chain patterns over time (analytics layer).A single user intent across an ERC-4337 UserOp.
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.