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,926,485The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 6,143,689 — 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 6,143,689 — 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 6,143,689 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,489.03/ETH
0.000547 ETH
$1.36
Direct transactionsTop-level transactions to or from this address: sent 0 / received 12. Activity through internal calls, events or token transfers is not counted here.
12
State changesHow many times this address's own account state changed — balance, nonce or code
10
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".
9
Nature 3Architecture 1Presence 2Derived 3
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contract0xe661...78d00xe661ac083165e49c100d66067c77bf19e05078d0deploy txblock 6,143,6892018-08-14 03:31 UTC
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 2 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
6,143,689First block where this address appeared in on-chain state· 2018-08-14 · 8.1y ago22,992,573Newest block across the activity streams the platform could consult, inbound included. Events 22,992,573 · Token transfers — none · Internal transfers 22,992,573 · Direct transactions 22,992,573· 2025-07-25 · 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,992,573 · Token transfers — none · Internal transfers 22,992,573 · Direct transactions 22,992,573
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
0xe661...78d00xe661ac083165e49c100d66067c77bf19e05078d010 dir · 9 int10 direct transactions, 9 with an internal call — reverts included, and one transaction can be several of these at once.In 9 of them this address was the sender, in 10 the recipient — one transaction can be both, so the two do not add up to the total.last ~407d agoLast: block 22,992,573 · ~2025-07-27. First ever: block 6,143,861 · ~2019-03-01. Dates estimated from the block distance.12 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x7c59...79860x7c59bc02fb160a3a0225d69e9fb125d328ed79862 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 ~407d agoLast: block 22,992,573 · ~2025-07-27. First ever: block 22,992,561 · ~2025-07-27. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.