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,280.11/ETH
7.0626 ETH
$16,103.65
Direct transactionsTop-level transactions to or from this address: sent 0 / received 51. Activity through internal calls, events or token transfers is not counted here.
51
State changesHow many times this address's own account state changed — balance, nonce or code
1.7K
Fees paidTotal gas fees this address has paid as a sender, all time.
0 ETH
Timeline
Activity (30d)
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 25,454,476 · Token transfers 25,720,621 · Internal transfers 25,085,321 · Direct transactions 25,454,476
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
Tokens
≈ $<0.01
2 tokens
ETH
$16,103.65
7.0626 ETH
Total (tokens + ETH)
≈ $16,103.66
CapabilitiesStructural abilities of the code, derived by the platform from bytecode and storage analysis
UpgradeableDelegatecalls to an implementation read from storage — behavior can change while the address stays the sameProxy: beaconDetected proxy family; detection confidence is a metric of the analysis, not trust2 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 contractEigenLayer Eigen Pod ManagerOfficial — verified contract: EigenLayer Eigen Pod Managerdeploy txblock 19,847,9282024-05-11 16:17 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x92cf...b7c80x92cfff81bd9d3ca540d3ee7e7d26a67b47fdb7c8
ImplementationThe implementation contract this proxy delegates toEigenLayer Eigen Pod BeaconOfficial — verified contract: EigenLayer Eigen Pod Beaconbeacon
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 35K contracts