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.HoldersWho holds this asset now, ranked by balance.PoolsDEX pools this asset trades in, and its recent volume.GraphMoney flow and structure around this address.
#25,917,940The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 24,117,752 — 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 24,117,752 — 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 24,117,752 — the earliest block among the facts that earned it.ERC-20 in codeThe ERC-20 selector set is present in the code that actually executes. Whether it has ever moved a token is a different fact — the "Token" chip, which is read from events. Derived unambiguously from chain data. Known from block 24,117,752 — the earliest block among the facts that earned it.Role: DEX poolClassed as a liquidity pool. Derived unambiguously from chain data. Known from block 24,117,752 — the earliest block among the facts that earned it.TokenA token contract — ERC-20, an NFT collection or ERC-1155; which one is listed with it. Derived unambiguously from chain data. Known from block 24,117,752 — the earliest block among the facts that earned it.Privileged functionsThe executing code exposes mint, pause or blacklist functions — presence in the dispatch table, NOT proof that they can be called now, or by whom. The ones found are listed with it. Derived unambiguously from chain data. Known from block 24,117,752 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,499.04/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 0. Activity through internal calls, events or token transfers is not counted here.
0
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
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".
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractUniswap V2: FactoryOfficial — verified contract: Uniswap V2: Factorydeploy txblock 24,117,7522025-12-29 10:37 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x8b56...bd500x8b5677fcd6370eba744f2d31b5d6b5b71f2ebd50
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 521K contracts
SemanticProtocol membership from curated address labeling
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
24,117,752First block where this address appeared in on-chain state· 2025-12-29 · 251d ago24,182,913Newest block across the activity streams the platform could consult, inbound included. Events 24,182,913 · Token transfers 24,182,913 · Internal transfers — none · Direct transactions — none· 2026-01-07 · 241d 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 24,182,913 · Token transfers 24,182,913 · Internal transfers — none · Direct transactions — none
Who moved value through this pool most often. 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,917,5989 of 9 counterparties
jaredfromsubway: MEV Bot 2jaredfromsubway: MEV Bot 2 (0x1f2f10d1c40777ae1da742455c65828ff36df387)44 tok44 with a token transfer — reverts included, and one transaction can be several of these at once.In 44 of them this address was the sender, in 44 the recipient — one transaction can be both, so the two do not add up to the total.last ~240d agoLast: block 24,182,799 · ~2026-01-08. First ever: block 24,119,010 · ~2025-12-30. Dates estimated from the block distance.44 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Uniswap V2: Router 2Official — verified contract: Uniswap V2: Router 238 tok38 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 (38); it sent nothing to the other.last ~240d agoLast: block 24,182,913 · ~2026-01-08. First ever: block 24,118,971 · ~2025-12-30. Dates estimated from the block distance.38 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x3fa1...31d60x3fa1c83dcc5ebb263719f3d2fdf12aeb0e6831d637 tok37 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 (37); it sent nothing to the other.last ~240d agoLast: block 24,182,913 · ~2026-01-08. First ever: block 24,118,971 · ~2025-12-30. Dates estimated from the block distance.37 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0xd60f...9ede0xd60feb1f56ef775d9ae302b63f359b69ee8b9ede36 tok36 with a token transfer — reverts included, and one transaction can be several of these at once.This address was the sender in all of them (36); it received nothing from the other.last ~240d agoLast: block 24,182,913 · ~2026-01-08. First ever: block 24,119,363 · ~2025-12-30. Dates estimated from the block distance.36 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV Bot: 0xfaeea8dfe730ea8595fbe3d8e35cb94ac19ddf7bMEV Bot: 0xfaeea8dfe730ea8595fbe3d8e35cb94ac19ddf7b (0xfaeea8dfe730ea8595fbe3d8e35cb94ac19ddf7b)36 tok36 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 (36); it sent nothing to the other.last ~240d agoLast: block 24,182,913 · ~2026-01-08. First ever: block 24,119,363 · ~2025-12-30. Dates estimated from the block distance.36 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV Bot: 0x6dc7...a7fMEV Bot: 0x6dc7...a7f (0x6dc71298ce1b61ba4c83d5cdf4b3b1e9aa558a7f)10 tok10 with a token transfer — reverts included, and one transaction can be several of these at once.In 10 of them this address was the sender, in 10 the recipient — one transaction can be both, so the two do not add up to the total.last ~240d agoLast: block 24,182,668 · ~2026-01-08. First ever: block 24,119,181 · ~2025-12-30. Dates estimated from the block distance.10 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Uniswap V4: PoolManagerOfficial — verified contract: Uniswap V4: PoolManager1 tok1 with a token transfer — 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 ~249d agoLast: block 24,119,003 · ~2025-12-30. First ever: block 24,119,003 · ~2025-12-30. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV Bot: 0xd41f60dc2e3693a9bce68674e055f4958321c0bdMEV Bot: 0xd41f60dc2e3693a9bce68674e055f4958321c0bd (0xd41f60dc2e3693a9bce68674e055f4958321c0bd)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 ~249d agoLast: block 24,119,003 · ~2025-12-30. First ever: block 24,119,003 · ~2025-12-30. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x7b4e...01cb0x7b4e9914c7f8189ce89f1e24a7f5729e936b01cb1 tok1 with a token transfer — 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 ~249d agoLast: block 24,118,992 · ~2025-12-30. First ever: block 24,118,992 · ~2025-12-30. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.