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,871,507The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 18,883,775 — 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 18,883,775 — 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 18,883,775 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,438.12/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 8. Activity through internal calls, events or token transfers is not counted here.
8
State changesHow many times this address's own account state changed — balance, nonce or code
12
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".
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 18,883,7752023-12-28 11:20 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x38ec...9e500x38ec351371a27bd7a5b75bf23fab23e162b19e50
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
16,308,159First block where this address appeared in on-chain state· 2022-12-31 · 3.7y ago22,148,455Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers 22,148,455 · Internal transfers 21,242,429 · Direct transactions 21,045,651· 2025-03-28 · 1.4y ago
1.4y silent
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,148,455 · Internal transfers 21,242,429 · Direct transactions 21,045,651
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,871,3179 of 9 counterparties
beaverbuildbeaverbuild (0x95222290dd7278aa3ddd389cc1e1d165cc4bafe5)3 dir3 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (3); it sent nothing to the other.last ~670d agoLast: block 21,045,651 · ~2024-10-29. First ever: block 16,529,206 · ~2023-02-10. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
TUPProxyTUPProxy (0x72b4c52f18f52eba3e4290a002df7c387427b058)2 int2 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 (2); it received nothing from the other.last ~642d agoLast: block 21,242,429 · ~2024-11-26. First ever: block 18,883,775 · ~2024-01-03. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
builder0x69builder0x69 (0x690b9a9e9aa1c9db991c7721a92d351db4fac990)2 dir2 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (2); it sent nothing to the other.last ~1074d agoLast: block 18,134,051 · ~2023-09-21. First ever: block 16,308,159 · ~2023-01-10. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
rsync-builderrsync-builder (0x1f9090aae28b8a3dceadf281b0f12828e676c326)2 dir2 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (2); it sent nothing to the other.last ~1093d agoLast: block 18,001,476 · ~2023-09-02. First ever: block 16,989,589 · ~2023-04-15. Dates estimated from the block distance.2 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 ~517d agoLast: block 22,148,455 · ~2025-03-31. First ever: block 22,148,455 · ~2025-03-31. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
eth-buildereth-builder (0xfeebabe6b0418ec13b30aadf129f5dcdd4f70cea)1 dir1 direct transactions — 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 ~1176d agoLast: block 17,397,970 · ~2023-06-11. First ever: block 17,397,970 · ~2023-06-11. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV Bot: 0x000...248MEV Bot: 0x000...248 (0x0000000000a84d1a9b0063a910315c7ffa9cd248)1 int1 with an internal call — 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 ~1181d agoLast: block 17,365,987 · ~2023-06-06. First ever: block 17,365,987 · ~2023-06-06. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV Bot: 0x07b...163MEV Bot: 0x07b...163 (0x07bae765074790b76c791834ab873be27493c163)1 int1 with an internal call — 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 ~1181d agoLast: block 17,365,987 · ~2023-06-06. First ever: block 17,365,987 · ~2023-06-06. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
MEV Bot: 0x83e...600MEV Bot: 0x83e...600 (0x83ef3d446bd1220c8261251f83ac5cc51311d600)1 int1 with an internal call — 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 ~1181d agoLast: block 17,365,987 · ~2023-06-06. First ever: block 17,365,987 · ~2023-06-06. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.