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.
#25,865,507The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 25,609,682 — 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 25,609,682 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,458.78/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 2. Activity through internal calls, events or token transfers is not counted here.
2
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 ETH
Activity (30d)Days this address changed state over the last 30 — height is how many blocks that day, not value moved.
ActiveActive within the last year — counting transactions, internal calls, events and token transfers
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 3Derived 2
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contract0x9d4c...f6750x9d4c8faeaddddeee1ed0c92dabad815c2484f675deploy txblock 25,609,6822026-07-25 12:08 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0xe439...394f0xe43944421681170648e10007f73816e04f74394f
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract
Timeline
25,609,682First block where this address appeared in on-chain state· 2026-07-25 · 35d ago25,635,115Newest block across the activity streams the platform could consult, inbound included. Events 25,635,115 · Token transfers — none · Internal transfers 25,635,115 · Direct transactions 25,635,115· 2026-07-29 · 32d ago
32d silent
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 25,635,115 · Token transfers — none · Internal transfers 25,635,115 · Direct transactions 25,635,115
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,865,2692 of 2 counterparties
0xe439...394f0xe43944421681170648e10007f73816e04f74394f2 dir · 1 int2 direct transactions, 1 with an internal call — reverts included, and one transaction can be several of these at once.In 1 of them this address was the sender, in 2 the recipient — one transaction can be both, so the two do not add up to the total.last ~31d agoLast: block 25,635,115 · ~2026-07-29. First ever: block 25,609,992 · ~2026-07-25. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x9d4c...f6750x9d4c8faeaddddeee1ed0c92dabad815c2484f6751 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 ~35d agoLast: block 25,609,682 · ~2026-07-25. First ever: block 25,609,682 · ~2026-07-25. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.