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.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.
#25,931,027The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 19,622,372 — 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 19,622,372 — the earliest block among the facts that earned it.Minimal proxy (EIP-1167)An immutable reference to an implementation, embedded in the code itself. Derived unambiguously from chain data. Known from block 19,622,372 — 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 19,622,372 — 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 25,768,427 — 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 19,622,372 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,489.03/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 5. Activity through internal calls, events or token transfers is not counted here.
5
State changesHow many times this address's own account state changed — balance, nonce or code
1
Fees paidTotal gas fees this address has paid as a sender, all time.
0 ETH
DormantNo activity of any kind for over a year — transactions, internal calls, events and token transfers alike
Chain factsDerived unambiguously from chain data. Each fact is stated only when it was proven — a fact that is absent was not proven, which is not the same as "no".
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractTokenVotingSetupTokenVotingSetup (0x644d3ba8a335f5b1a6affe63e551306d0c933582)deploy txblock 19,622,3722024-04-10 02:52 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x8f98...ac9e0x8f988ab99c40333f54f0a8fa1de1e4417777ac9e
ImplementationThe implementation contract this proxy delegates toGovernanceERC20GovernanceERC20 (0x868581ee5991c6c08d2467132698fa4ab6c9c272)eip1167
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 135 contracts
Timeline
LondonLondon · block 12,965,000. EIP-1559: blocks carry a base fee, and part of every fee is burnt.MergeMerge · block 15,537,394. Proof of stake. Difficulty goes to zero and block times settle at 12 seconds.ShapellaShapella · block 17,034,871. Validator withdrawals begin — the first stake leaves the beacon chain.DencunDencun · block 19,426,587. EIP-4844: blob-carrying transactions, with their own gas market.PectraPectra · block 22,431,084. EIP-7702: an EOA can carry a delegation to contract code.FusakaFusaka · block 23,935,694. Blob capacity steps up on a schedule of its own (BPO), past the Pectra ceiling.
5M10M15M20M25M
19,622,372First block where this address appeared in on-chain state· 2024-04-10 · 2.4y ago22,957,459Newest block across the activity streams the platform could consult, inbound included. Events 22,957,459 · Token transfers — none · Internal transfers — none · Direct transactions 22,957,459· 2025-07-20 · 1.1y ago
First seenFirst block where this address appeared in on-chain state
Last activeNewest block across the activity streams the platform could consult, inbound included. Events 22,957,459 · Token transfers — none · Internal transfers — none · Direct transactions 22,957,459
Who moved this token most often. Ranked by how OFTEN the two interacted, not by how much value passed — that is the Graph. Ordered, not numbered: hundreds can sit tied at the tail.Every interaction the graph holds, as of the block named beside itall time · as of block 25,925,0502 of 2 counterparties
0x8f98...ac9e0x8f988ab99c40333f54f0a8fa1de1e4417777ac9e4 dir4 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (4); it sent nothing to the other.last ~412d agoLast: block 22,957,459 · ~2025-07-23. First ever: block 20,618,653 · ~2024-09-01. Dates estimated from the block distance.4 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x14e4...efa10x14e4093783c00cbb5125d605f11fcecb1dd6efa11 dir1 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (1); it sent nothing to the other.last ~735d agoLast: block 20,626,086 · ~2024-09-02. First ever: block 20,626,086 · ~2024-09-02. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.