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.HoldersWho holds this asset now, ranked by balance.PoolsDEX pools this asset trades in, and its recent volume.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.Was an NFT collectionAt least ten ERC-721 Transfers were observed over this address's lifetime. A statement about history — the contract need not still carry the interface. Derived unambiguously from chain data.Transfers state-backedThis token's Transfer events are backed by matching state changes in the issuer's storage. Derived unambiguously from chain data.
BalanceNative ETH balance of this address, valued at $2,246.64/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 15. Activity through internal calls, events or token transfers is not counted here.
15
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 25,774,051 · Token transfers — none · Internal transfers — none · Direct transactions 25,013,896
ActiveActive within the last year — counting transactions, internal calls, events and token transfersNo active blacklistsChecked against known issuer blacklists — none currently lists this address
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 contractPayableBeaconFactoryPayableBeaconFactory (0x5531f96bb9e9559ae9880cc0109e06ef477aef8e)deploy txblock 19,324,1362024-02-28 06:06 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x55c0...013e0x55c09707fd7afd670e82a62faee312903940013e
ImplementationThe implementation contract this proxy delegates toUpgradeableBeaconUpgradeableBeacon (0x0cce1806ff2f01871a1a4b0ad3aa087ccb04f423)beacon
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 161 contracts