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.GraphMoney flow and structure around this address.
#25,924,940The chain head this page was rendered at.
AddressAn externally owned account: a key, not code. Derived unambiguously from chain data. Known from block 25,662,415 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,492.45/ETH
< 0.000001 ETH
$<0.01
Direct transactionsTop-level transactions to or from this address: sent 1 / received 0. Activity through internal calls, events or token transfers is not counted here.
1
NonceThe account nonce. Close to the number of transactions this account sent, but not equal to it — since Pectra an EIP-7702 authorisation also increments it. Not the counter above, which also includes transactions received.
1
State changesHow many times this address's own account state changed — balance, nonce or code
2
Fees paidTotal gas fees this address has paid as a sender, all time.
< 0.000001 ETH
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".
5
Nature 2Presence 2Derived 1
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
25,662,415First block where this address appeared in on-chain state· 2026-08-01 · 36d ago25,662,416Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers — none · Internal transfers 25,662,415 · Direct transactions 25,662,416· 2026-08-01 · 36d 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 — none · Token transfers — none · Internal transfers 25,662,415 · Direct transactions 25,662,416
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,924,8072 of 2 counterparties
0x0cd9...4c330x0cd996456c723da78b28d6347d8d452838464c331 dir1 direct transactions — reverts included, and one transaction can be several of these at once.This address was the sender in all of them (1); it received nothing from the other.last ~36d agoLast: block 25,662,416 · ~2026-08-02. First ever: block 25,662,416 · ~2026-08-02. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Suspicious addressphishing1 int1 with an internal call — 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 ~36d agoLast: block 25,662,415 · ~2026-08-02. First ever: block 25,662,415 · ~2026-08-02. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.