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.Fungible tokenAn ERC-20 surface on the code that actually executes (decimals, symbol, name, totalSupply), at least one observed ERC-20 Transfer, and zero ERC-721/1155 events. Says what the interface is — not whether the token is legitimate. Derived unambiguously from chain data.
BalanceNative ETH balance of this address, valued at $2,250.54/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 176. Activity through internal calls, events or token transfers is not counted here.
176
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,600,658 · Token transfers 25,600,658 · Internal transfers — none · Direct transactions 25,600,658
No 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: unknownDetected proxy family; detection confidence is a metric of the analysis, not trust10 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 contract0x8d6f...f9b10x8d6f5479b14348186fae9bc7e636e947c260f9b1deploy txblock 24,296,7472026-01-23 09:59 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x8e65...9bbf0x8e65743e23ed13f593e7d4eb7ed3dde1e1cb9bbf
ImplementationThe implementation contract this proxy delegates toVaultVault (0xe50554ec802375c9c3f9c087a8a7bb8c26d3dedf)unknown
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract