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.
High traffic→Very high transaction volume (≥ 100,000 txns).
BalanceNative ETH balance of this address, valued at $2,113.93/ETH
0.035302 ETH
$74.63
Direct transactionsTop-level transactions to or from this address: sent 0 / received 2M. Activity through internal calls, events or token transfers is not counted here.
2M
State changesHow many times this address's own account state changed — balance, nonce or code
44
Fees paidTotal gas fees this address has paid as a sender, all time.
0 ETH
Timeline
Activity (30d)
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,791,513 · Token transfers 25,791,522 · Internal transfers 25,791,583 · Direct transactions 25,791,522
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
≈ $10,483.58
34 of 39 tokens
ETH
$74.63
0.035302 ETH
Total (tokens + ETH)
≈ $10,558.20
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: diamond_likeDetected proxy family; detection confidence is a metric of the analysis, not trust1 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 contractcreate2Deployercreate2Deployer (0x13b0d85ccb8bf860b6b79af3029fca081ae9bef2)deploy txblock 19,958,3982024-05-27 03:03 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0xee7b...4ae80xee7b429ea01f76102f053213463d4e95d5d24ae8
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 2 contracts