Bytecode Disassembler
Runs offlineDisassemble EVM bytecode into opcodes.
runtime or creation code
13 instructions16 bytes1 jump destinations
| 0000 | PUSH1 | 0x80 |
| 0002 | PUSH1 | 0x40 |
| 0004 | MSTORE | |
| 0005 | CALLVALUE | |
| 0006 | DUP1 | |
| 0007 | ISZERO | |
| 0008 | PUSH1 | 0x0e |
| 000a | JUMPI | |
| 000b | PUSH0 | |
| 000c | DUP1 | |
| 000d | REVERT | |
| 000e | JUMPDEST | |
| 000f | POP |
Offsets are hex byte positions — the same numbers a JUMP targets, and the ones a stack trace refers to. Creation code contains the constructor followed by the runtime code it returns, so the second half is what actually ends up deployed.
About bytecode disassembler
Compiled contracts are a flat run of bytes, each one an instruction, with PUSH instructions carrying their data inline. Disassembling recovers the instruction boundaries and names, which is enough to find jump destinations, spot the function dispatcher at the start, and see roughly what a contract does when no verified source is available. Creation code contains a constructor followed by the runtime code it returns — the second part is what actually gets deployed.