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,920,670The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 20,686,933 — 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 20,686,933 — the earliest block among the facts that earned it.Key-controlledThe owner is a plain account: one private key can do whatever the owner role allows here. Derived unambiguously from chain data. Known from block 20,686,933 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,490.28/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 4. Activity through internal calls, events or token transfers is not counted here.
4
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 contract0x9dec...c12d0x9dec4b2816eaa9a3793a634f0ad046bae8a4c12ddeploy txblock 20,686,9332024-09-05 20:59 UTC
Owned byThe current owner of this contract, by its last ownership transfer (OpenZeppelin Ownable). Role-based access control is a different pattern and is not covered by this.0x9dec...c12d0x9dec4b2816eaa9a3793a634f0ad046bae8a4c12dseen at 20,686,933Where the platform last observed this owner. Not a start: no history is built for this relation.
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
20,686,933First block where this address appeared in on-chain state· 2024-09-05 · 2.0y ago22,044,587Newest block across the activity streams the platform could consult, inbound included. Events 20,690,393 · Token transfers 22,044,587 · Internal transfers 20,690,393 · Direct transactions 20,690,393· 2025-03-14 · 1.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 20,690,393 · Token transfers 22,044,587 · Internal transfers 20,690,393 · Direct transactions 20,690,393
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,918,7225 of 5 counterparties
0x9dec...c12d0x9dec4b2816eaa9a3793a634f0ad046bae8a4c12d4 dir · 2 int4 direct transactions, 2 with an internal call — reverts included, and one transaction can be several of these at once.In 2 of them this address was the sender, in 4 the recipient — one transaction can be both, so the two do not add up to the total.last ~726d agoLast: block 20,690,393 · ~2024-09-10. First ever: block 20,686,991 · ~2024-09-10. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded. 1 more reverted.
Uniswap V2: Router 2Official — verified contract: Uniswap V2: Router 23 int3 with an internal call — reverts included, and one transaction can be several of these at once.In 3 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 ~726d agoLast: block 20,690,393 · ~2024-09-10. First ever: block 20,686,991 · ~2024-09-10. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded. 1 more reverted.
0x0a4c...4c760x0a4c79ce84202b03e95b7a692e5d728d83c44c761 nft1 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 ~538d agoLast: block 22,044,587 · ~2025-03-17. First ever: block 22,044,587 · ~2025-03-17. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Uniswap V2: MONKEY/WETHUniswap V2: MONKEY/WETH (0x5f801fdf208c67eac2720c46e464af535c86d03d)1 tok1 with a token transfer — reverts included, and one transaction can be several of these at once.In 1 of them this address was the sender, in 1 the recipient — one transaction can be both, so the two do not add up to the total.last ~726d agoLast: block 20,690,393 · ~2024-09-10. First ever: block 20,690,393 · ~2024-09-10. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Uniswap V2: Neiro/WETHUniswap V2: Neiro/WETH (0x3885fbe4cd8aed7b7e9625923927fa1ce30662a3)1 tok1 with a token transfer — reverts included, and one transaction can be several of these at once.In 1 of them this address was the sender, in 1 the recipient — one transaction can be both, so the two do not add up to the total.last ~726d agoLast: block 20,687,400 · ~2024-09-10. First ever: block 20,687,400 · ~2024-09-10. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.