Smart contract — an account with deployed bytecode.
eip7702
Detected proxy pattern: eip7702.
0x55f2f094e6c5565564ee026c353fd1fb3803b3fbView as Contract →Created at block 23,262,040(31 Aug 2025) · 36 state changesCounts only this address’s own state-changing activity (e.g. its deployment), not inbound calls from other accounts. For truthful latest activity see “Last Active” above or the Transactions tab.
Balance
0.000144 ETH
≈ $0.25 · $1,745.31/ETH
Transactions
13
Sent: 11 / Received: 2
Account Type
Contract
23 bytes
Last ActiveLatest block where this address took part in any transaction — sender or receiver, inbound included. Distinct from its last own state-change, which freezes at the deploy block for called contracts.
The proxy standard this contract was matched to (e.g. EIP-1967, UUPS, transparent, EIP-1167).·Classification confidence 3/3How confidently static bytecode analysis matched this contract to a KNOWN proxy standard (0–3). This is a classifier certainty — NOT a trust or safety score for the contract.
Capabilities
Upgradeable
Whether the contract's logic can be replaced behind a proxy (admin-controlled implementation). (absent)
Delegatecall
Whether the contract uses DELEGATECALL — running another contract's code in its own storage context. (absent)
Callcode
Whether the contract uses the legacy CALLCODE opcode (deprecated and security-sensitive). (absent)
EIP-1167 Proxy
Whether this is an EIP-1167 minimal proxy — a tiny clone that delegates all calls to a fixed implementation. (absent)
EIP-7702 Delegation
Whether this EOA has an EIP-7702 code delegation set (the account temporarily runs contract code). (present)
Storage Changes
0
Number of storage-slot changes observed for this contract.
Active Delegations
0
Currently-active EIP-7702 delegations pointing at this code.
Selectors
0
Distinct 4-byte function selectors exposed by the bytecode.