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,922,654The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 4,438,420 — 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 4,438,420 — 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 4,438,420 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,514.46/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 6. Activity through internal calls, events or token transfers is not counted here.
6
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".
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 contractBitstamp 2Bitstamp 2 (0x1522900b6dafac587d499a862861c0869be6e428)deploy txblock 4,438,4202017-10-27 09:12 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transactionBitstamp 1Bitstamp 1 (0x00bdb5699745f5b860228c8f939abf1b9ae374ed)
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1.2M 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
4,438,420First block where this address appeared in on-chain state· 2017-10-27 · 8.9y ago6,760,215Newest block across the activity streams the platform could consult, inbound included. Events 6,760,215 · Token transfers — none · Internal transfers 6,760,215 · Direct transactions 6,760,215· 2018-11-23 · 7.8y 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 6,760,215 · Token transfers — none · Internal transfers 6,760,215 · Direct transactions 6,760,215
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,922,4014 of 4 counterparties
Bitstamp 2Bitstamp 2 (0x1522900b6dafac587d499a862861c0869be6e428)6 int6 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 (6); it received nothing from the other.last ~2661d agoLast: block 6,760,215 · ~2019-05-25. First ever: block 4,550,174 · ~2018-07-22. Dates estimated from the block distance.6 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x45ce...b1c40x45ce411e9ba3dce1209ee450a2bd0b533752b1c43 dir3 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (3); it sent nothing to the other.last ~2661d agoLast: block 6,758,017 · ~2019-05-25. First ever: block 6,756,144 · ~2019-05-25. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x6796...e7ca0x6796f8164365fb7a4464a905b39f996bd4a3e7ca2 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 ~2661d agoLast: block 6,760,215 · ~2019-05-25. First ever: block 6,756,450 · ~2019-05-25. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0xa736...9f200xa736d1e54290a177d412cf477fa440ccf8809f201 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 ~2968d agoLast: block 4,550,174 · ~2018-07-22. First ever: block 4,550,174 · ~2018-07-22. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.