EVM contract bytecode facts on 16 chains: code hash and size, proxy type and imp...

{ "method": "GET", "queryParams": { "address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", "chain": "ethereum" }, "type": "http" }

{ "example": { "address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", "chain": "ethereum", "chain_id": 1, "code_hash": "0xd80d4b7c890cb9d6a4893e6b52bc34b56b25335cb13716e0d1d31383e6b41505", "code_size_bytes": 2186, "function_selector_count": 5, "function_selectors": [ { "name": "upgradeTo(address)", "selector": "0x3659cfe6" }, { "name": "upgradeToAndCall(address,bytes)", "selector": "0x4f1ef286" }, { "name": null, "selector": "0x5c60da1b" }, { "name": null, "selector": "0x8f283970" }, { "name": null, "selector": "0xf851a440" } ], "implementation": "0x43506849D7C04F9138D1A2050bbF3A0c054402dd", "is_proxy": true, "note": "Static facts from the deployed bytecode via chain RPC. Selectors are extracted from the dispatcher (PUSH4 ... EQ), so a few unusual contracts may show fewer. name is filled only for selectors in a small built-in table; resolve others with the contract/abi route when the contract is verified. opcode_flags come from walking the instruction stream, but code reached only through data or jumps can still be misread, so treat them as hints, not findings. A delegatecall opcode is normal in proxies and libraries.", "opcode_flags": { "has_delegatecall_opcode": true, "has_selfdestruct_opcode": false }, "proxy_admin": "0x807a96288A1A408dBC13DE2b1d087d10356395d2", "proxy_type": "storage-slot proxy (EIP-1967 / ZeppelinOS / EIP-1822)", "selectors_truncated": false, "source": "Chain JSON-RPC (ethereum)" }, "type": "json" }