EVM bytecode inspector
Paste the runtime code of a contract (eth_getCode) to see what kind of code it is, where a proxy or delegation points, and what is inside.
Try an example:Minimal proxy
It recognises EIP-1167 minimal proxies (and their implementation), EIP-7702 account delegations (and the delegate), and EOF containers. It reports the code size against the EIP-170 limit of 24,576 bytes and the code's keccak-256 hash.
For ordinary contracts it reads the Solidity metadata trailer (compiler version and IPFS hash), counts notable opcodes like DELEGATECALL, CREATE2 and SELFDESTRUCT, and lists 4-byte values that look like function selectors. The selector list is a heuristic, not a guarantee.
AI agents can run this through the SwapChan MCP tool bytecode_inspect. Set up MCP
FAQ
- Where do I get the bytecode?
- From a block explorer's contract page, or eth_getCode on any RPC. Use the deployed runtime code, not the creation code.
- Why does it say selector candidates?
- Selectors are guessed from the code's dispatch pattern. Most are real, but compilers can produce look-alikes.
- What is an EIP-7702 delegation?
- Code that makes an ordinary account run another contract's code. The page shows which contract it points to.
- Is it safe?
- Yes. It only reads public data you paste. Nothing is stored or logged, and you never need a private key or seed phrase here.