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.
ContractThe address currently carries runtime code. Derived unambiguously from chain data.Had runtime codeRuntime code existed at this address at some point of its history. Derived unambiguously from chain data.
BalanceNative ETH balance of this address, valued at $2,498.14/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 4. Activity through internal calls, events or token transfers is not counted here.
4
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
Timeline
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 22,477,294 · Token transfers — none · Internal transfers 22,477,294 · Direct transactions 22,477,294
DormantNo activity of any kind for over a year — transactions, internal calls, events and token transfers alikeNo active blacklistsChecked against known issuer blacklists — none currently lists this address
Portfolio
ETH
$0.00
0 ETH
Total (shown tokens + ETH)
≈ $0.00
CapabilitiesStructural abilities of the code, derived by the platform from bytecode and storage analysis
No proxy or upgrade mechanics detectedStatic analysis found no delegatecall-based upgrade path or proxy mechanics in the runtime bytecode
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractUnichain DisputeGameFactoryProxyOfficial — verified contract: Unichain DisputeGameFactoryProxydeploy txblock 22,402,6552025-05-03 10:27 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0xd5f0...fa9a0xd5f0e2912c70771c589cd8bb087ede0dab4afa9a
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract
Top counterparties
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,853,9084 of 4 counterparties
0x9509...1be70x950983f83cc3957664ba0ffb5780db06d7fd1be74 dir4 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (4); it sent nothing to the other.last ~468d agoLast: block 22,477,294 · ~2025-05-16. First ever: block 22,427,641 · ~2025-05-09. Dates estimated from the block distance.4 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Impersonates WETHMalicious addressImpersonates: WETH · impersonation, address_poisoning2 int2 with an internal call — reverts included, and one transaction can be several of these at once.In 1 of them this address was the sender, in 1 the recipient — one transaction can be both, so the two do not add up to the total.last ~468d agoLast: block 22,477,294 · ~2025-05-16. First ever: block 22,402,655 · ~2025-05-06. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0xd5f0...fa9a0xd5f0e2912c70771c589cd8bb087ede0dab4afa9a1 int1 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 (1); it received nothing from the other.last ~468d agoLast: block 22,477,294 · ~2025-05-16. First ever: block 22,477,294 · ~2025-05-16. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Unichain DisputeGameFactoryProxyOfficial — verified contract: Unichain DisputeGameFactoryProxy1 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 ~479d agoLast: block 22,402,655 · ~2025-05-06. First ever: block 22,402,655 · ~2025-05-06. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.