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,916,734The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 22,288,674 — 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 22,288,674 — 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 22,288,674 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,506.75/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 871. Activity through internal calls, events or token transfers is not counted here.
871
State changesHow many times this address's own account state changed — balance, nonce or code
872
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".
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 contract0x4b4f...922c0x4b4fcf6130b99d53c81a3e212a6f7b6b5d37922cdeploy txblock 22,288,6742025-04-17 12:19 UTC
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 361 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
22,288,674First block where this address appeared in on-chain state· 2025-04-17 · 1.4y ago25,436,752Newest block across the activity streams the platform could consult, inbound included. Events 25,436,752 · Token transfers 24,792,079 · Internal transfers — none · Direct transactions 25,436,752· 2026-07-01 · 66d 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 25,436,752 · Token transfers 24,792,079 · Internal transfers — none · Direct transactions 25,436,752
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,916,4342 of 2 counterparties
0x4b4f...922c0x4b4fcf6130b99d53c81a3e212a6f7b6b5d37922c871 dir871 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (871); it sent nothing to the other.last ~66d agoLast: block 25,436,752 · ~2026-07-01. First ever: block 22,331,696 · ~2025-04-26. Dates estimated from the block distance.871 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
HexDotComHexDotCom (0x6357d3843d715496257e338a878ab0b72040a918)1 tok1 with a token transfer — 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 ~156d agoLast: block 24,792,079 · ~2026-04-03. First ever: block 24,792,079 · ~2026-04-03. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.