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,925,347The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 7,178,973 — 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 7,178,973 — 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 7,178,973 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,489.03/ETH
0.018690 ETH
$46.52
Direct transactionsTop-level transactions to or from this address: sent 0 / received 74. Activity through internal calls, events or token transfers is not counted here.
74
State changesHow many times this address's own account state changed — balance, nonce or code
8
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 contract0x0d68...f9da0x0d68c987edb915cc729cd754788205d5bfa5f9dadeploy txblock 7,178,9732019-02-05 15:53 UTC
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract
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
7,178,973First block where this address appeared in on-chain state· 2019-02-05 · 7.6y ago7,183,349Newest block across the activity streams the platform could consult, inbound included. Events 7,183,349 · Token transfers — none · Internal transfers 7,183,349 · Direct transactions 7,183,349· 2019-02-06 · 7.6y 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 7,183,349 · Token transfers — none · Internal transfers 7,183,349 · Direct transactions 7,183,349
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,0506 of 6 counterparties
0x0d68...f9da0x0d68c987edb915cc729cd754788205d5bfa5f9da52 dir · 1 int52 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 52 the recipient — one transaction can be both, so the two do not add up to the total.last ~2603d agoLast: block 7,183,349 · ~2019-07-23. First ever: block 7,179,115 · ~2019-07-22. Dates estimated from the block distance.50 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded. 2 more reverted.
0x3490...10590x3490ae3a80d122c759f77ffd78c35c25d970105916 dir · 1 int16 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 16 the recipient — one transaction can be both, so the two do not add up to the total.last ~2603d agoLast: block 7,183,349 · ~2019-07-23. First ever: block 7,179,204 · ~2019-07-22. Dates estimated from the block distance.13 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded. 3 more reverted.
0x97f9...d5c40x97f9effbd56f8c16b2f07e86fc32ad4241eed5c42 dir2 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (2); it sent nothing to the other.last ~2603d agoLast: block 7,180,596 · ~2019-07-23. First ever: block 7,180,368 · ~2019-07-23. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x79d8...ff960x79d8b30554f75dc40ae734407c185e7dc974ff962 dir2 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (2); it sent nothing to the other.last ~2603d agoLast: block 7,179,736 · ~2019-07-22. First ever: block 7,179,210 · ~2019-07-22. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x0b71...f1570x0b7129d6ec72473e35be0a9e2a7ae2cce6fbf1572 dir2 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (2); it sent nothing to the other.last ~2603d agoLast: block 7,180,280 · ~2019-07-23. First ever: block 7,180,277 · ~2019-07-23. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded. 1 more reverted.
Fomo3D: Contract 3Fomo3D: Contract 3 (0xc7029ed9eba97a096e72607f4340c34049c7af48)1 int1 with an internal call — 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 ~2603d agoLast: block 7,179,822 · ~2019-07-22. First ever: block 7,179,822 · ~2019-07-22. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.