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 27. Activity through internal calls, events or token transfers is not counted here.
27
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,792,745 · Token transfers 25,792,745 · Internal transfers — none · Direct transactions 25,791,860
No active blacklistsChecked against known issuer blacklists — none currently lists this address
Portfolio
Tokens
≈ $<0.01
1 tokens
ETH
$0.00
0 ETH
Total (tokens + ETH)
≈ $<0.01
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 bytecode91 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 contract0xf027...66e00xf027193b16ec30b6885d49a25fc84173bea766e0deploy txblock 22,431,8042025-05-07 12:37 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x51c8...11250x51c83b1e82f2d98d77a8694a2a8b553f6eda1125
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract