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,290The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 11,253,770 — 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 11,253,770 — 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 11,253,770 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,489.03/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 64. Activity through internal calls, events or token transfers is not counted here.
64
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 contractMEV BotMEV Bot (0x131a99859a8bfa3251d899f0675607766736ffae)deploy txblock 11,253,7702020-11-14 04:52 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x38c7...d2020x38c7ea86c8235b0cfccfb91153259e85353cd202
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
11,253,770First block where this address appeared in on-chain state· 2020-11-14 · 5.8y ago14,258,710Newest block across the activity streams the platform could consult, inbound included. Events 14,258,710 · Token transfers — none · Internal transfers 14,258,710 · Direct transactions 14,258,710· 2022-02-22 · 4.5y 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 14,258,710 · Token transfers — none · Internal transfers 14,258,710 · Direct transactions 14,258,710
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
2Miners: PPLNS2Miners: PPLNS (0x00192fb10df37c9fb26829eb2cc623cd1bf599e8)64 dir64 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (64); it sent nothing to the other.last ~1620d agoLast: block 14,258,710 · ~2022-04-01. First ever: block 11,456,988 · ~2021-03-08. Dates estimated from the block distance.64 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV BotMEV Bot (0x131a99859a8bfa3251d899f0675607766736ffae)64 int64 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 (64); it received nothing from the other.last ~1620d agoLast: block 14,258,710 · ~2022-04-01. First ever: block 11,456,988 · ~2021-03-08. Dates estimated from the block distance.64 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.