OverviewWhat this address is, since when, and how it is doing.ActivityEverything that happened here — transactions, transfers, internal calls, state changes.StorageContract storage activity: slots written, who writes them, how deep the calls go.EventsThe event log this contract itself emitted, decoded where the ABI is known.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,253.62/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
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
No 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 bytecode19 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 contractCreate2: Deterministic Deployment ProxyCreate2: Deterministic Deployment Proxy (0x4e59b44847b379578588920ca78fbf26c0b4956c)deploy txblock 24,765,0122026-03-29 18:23 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x0ed3...859a0x0ed35b1609ec45c7079e80d11149a52717e4859a
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 2 contracts