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.GraphMoney flow and structure around this address.
#25,930,581The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 19,978,947 — 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 19,978,947 — the earliest block among the facts that earned it.Minimal proxy (EIP-1167)An immutable reference to an implementation, embedded in the code itself. Derived unambiguously from chain data. Known from block 19,978,947 — 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
73
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".
10
Nature 3Architecture 2Presence 2Derived 3
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractTUPProxyTUPProxy (0x1e68238ce926dec62b3fbc99ab06eb1d85ce0270)deploy txblock 19,978,9472024-05-30 00:00 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x1fa1...5ed80x1fa15bc53e2ffa54fc6d7e011896bda584775ed8
ImplementationThe implementation contract this proxy delegates toFeeRecipientFeeRecipient (0x933fbfeb4ed1f111d12a39c2ab48657e6fc875c6)eip1167
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 41.7K 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
19,978,947First block where this address appeared in on-chain state· 2024-05-30 · 2.3y ago23,475,013Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers 23,256,178 · Internal transfers 23,475,013 · Direct transactions — none· 2025-09-30 · 342d 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 — none · Token transfers 23,256,178 · Internal transfers 23,475,013 · Direct transactions — none
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,0504 of 4 counterparties
TUPProxyTUPProxy (0xe8ec6f702d68ded71112031d78bbff959c7234c7)3 int3 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 (3); it received nothing from the other.last ~340d agoLast: block 23,475,013 · ~2025-10-02. First ever: block 19,978,947 · ~2024-06-04. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x4904...6bf20x4904667de23e03f25994c0965fab662afab46bf21 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 ~370d agoLast: block 23,256,178 · ~2025-09-02. First ever: block 23,256,178 · ~2025-09-02. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Visit website nano-eth .net to claim rewardsVisit website nano-eth .net to claim rewards (0x719097022b18bd1a3a9009910664f99362225158)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 ~370d agoLast: block 23,256,178 · ~2025-09-02. First ever: block 23,256,178 · ~2025-09-02. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0xd8d9...86040xd8d98ee915a5a4f52c40d97fcd8ffadea1ee86041 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 ~524d agoLast: block 22,149,131 · ~2025-04-01. First ever: block 22,149,131 · ~2025-04-01. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.