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,917,236The chain head this page was rendered at.
AddressAn externally owned account: a key, not code. Derived unambiguously from chain data. Known from block 24,555,870 — the earliest block among the facts that earned it.
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).
latest sliceNo window was asked for: this is the latest slice upstream serves — blocks 25,867,112 to 25,917,112, 50,001 blocks. Step to state both bounds yourself.25,867,112–25,917,112The same width, immediately before this windowTwice as far back, same endHalf as far back, same endThe same width, immediately after this window
Ledger: 2 counterpartiesLedger window only — unique counterparties in the latest transfers; the all-time aggregate is on its way from the data platform · 2 movements in 2 transactions · 2 ETH, 0 token · over 21h
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.