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,258.36/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
Last activeNewest block across the activity streams the platform could consult, inbound included. Events 25,171,535 · Token transfers — none · Internal transfers — none · Direct transactions — none
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
No proxy or upgrade mechanics detectedStatic analysis found no delegatecall-based upgrade path or proxy mechanics in the runtime bytecode15 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 contractMEV Bot: 0x5b5a...209MEV Bot: 0x5b5a...209 (0x5b5a0580bcfd3673820bb249514234afad33e209)deploy txblock 25,171,5352026-05-25 09:50 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x43de...80a50x43debe92a7a32dca999593fad617dbd2e6b080a5
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract