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,925,816The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 10,975,811 — 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 10,975,811 — 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 10,975,811 — 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 10,975,811 — the earliest block among the facts that earned it.Role: DEX poolClassed as a liquidity pool. Derived unambiguously from chain data. Known from block 10,975,811 — 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 10,975,811 — 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 10,975,811 — 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 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
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 10,975,8112020-10-02 09:26 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x3758...ccd70x37586a6b1076f4d38d9508e833e47631b2f2ccd7
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 521.1K 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
10,975,811First block where this address appeared in on-chain state· 2020-10-02 · 5.9y ago11,359,534Newest block across the activity streams the platform could consult, inbound included. Events 11,359,534 · Token transfers 11,359,534 · Internal transfers — none · Direct transactions — none· 2020-11-30 · 5.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 11,359,534 · Token transfers 11,359,534 · 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,925,0501 of 1 counterparties
0x3758...ccd70x37586a6b1076f4d38d9508e833e47631b2f2ccd73 tok3 with a token transfer — reverts included, and one transaction can be several of these at once.In 2 of them this address was the sender, in 3 the recipient — one transaction can be both, so the two do not add up to the total.last ~2022d agoLast: block 11,359,534 · ~2021-02-22. First ever: block 10,975,811 · ~2020-12-31. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.