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.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…
#25,938,226The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 24,539,458 — 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 24,539,458 — 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 24,539,458 — the earliest block among the facts that earned it.ERC-20 in codeThe ERC-20 selector set is present in the code that actually executes. Whether it has ever moved a token is a different fact — the "Token" chip, which is read from events. Derived unambiguously from chain data. Known from block 24,539,458 — the earliest block among the facts that earned it.Role: DEX poolClassed as a liquidity pool. Derived unambiguously from chain data. Known from block 24,539,458 — the earliest block among the facts that earned it.TokenA token contract — ERC-20, an NFT collection or ERC-1155; which one is listed with it. Derived unambiguously from chain data. Known from block 24,539,458 — the earliest block among the facts that earned it.Privileged functionsThe executing code exposes mint, pause or blacklist functions — presence in the dispatch table, NOT proof that they can be called now, or by whom. The ones found are listed with it. Derived unambiguously from chain data. Known from block 24,539,458 — 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.Structural relationships — deployer, implementation, same-bytecode, protocol.Recurring on-chain patterns over time (analytics layer).Interpreted actions (swap, supply, bridge) — arrives with the operations vitrine.
Token flow: 4 addressesLedger 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. · 7 transfers in 4 transactions · over 3d
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.