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,496.60/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 249. Activity through internal calls, events or token transfers is not counted here.
249
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 24,858,067 · Token transfers — none · Internal transfers 24,858,067 · Direct transactions 24,824,115
ActiveActive within the last year — counting transactions, internal calls, events and token transfersNo 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 bytecode21 functionsDistinct function selectors found in the runtime bytecode
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contract0xd9ca...aae50xd9caebb7dc51fbfb218073fc0de9d4d6440eaae5deploy txblock 23,638,5532025-10-23 06:55 UTC
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract