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,922,897The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 20,229,940 — 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,229,940 — 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 20,229,940 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,514.57/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
86
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".
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 20,229,9402024-07-04 01:42 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x7a55...052b0x7a555aae9dd9d7996ee85ade19043c572070052b
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
20,229,940First block where this address appeared in on-chain state· 2024-07-04 · 2.2y ago23,548,534Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers 22,062,322 · Internal transfers 23,548,534 · Direct transactions — none· 2025-10-10 · 331d 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 22,062,322 · Internal transfers 23,548,534 · 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,922,7042 of 2 counterparties
TUPProxyTUPProxy (0xe8ec6f702d68ded71112031d78bbff959c7234c7)5 int5 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 (5); it received nothing from the other.last ~329d agoLast: block 23,548,534 · ~2025-10-12. First ever: block 20,229,940 · ~2024-07-08. Dates estimated from the block distance.5 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
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 ~536d agoLast: block 22,062,322 · ~2025-03-19. First ever: block 22,062,322 · ~2025-03-19. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.