OverviewWhat this address is, since when, and how it is doing.ActivityEverything that happened here — transactions, transfers, internal calls, state and storage changes, emitted events.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,316.75/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 1.1K. Activity through internal calls, events or token transfers is not counted here.
1.1K
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 — none · Token transfers 23,526,884 · Internal transfers 23,526,884 · Direct transactions 23,526,884
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
≈ $4,885.87
1 tokens
ETH
$0.00
0 ETH
Total (tokens + ETH)
≈ $4,885.87
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 bytecode32 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 contract0x6b8a...f51e0x6b8a5b3952a9836bc8f923483bfd6852e98af51edeploy txblock 23,486,0632025-10-01 22:55 UTC
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract