Bytecode Disassembler
Opcodes, offsets and immediates from EVM bytecode.
Runs offline
Paste EVM bytecode to list opcodes, offsets and immediates.
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.
Common questions
How do I read EVM bytecode as opcodes?
Paste the runtime or creation bytecode. This walks each byte into opcodes, immediate values and offsets so you can see JUMPDESTs, PUSH data and call patterns without a full decompiler.
Is a disassembly the same as verified source?
No. Disassembly is the instructions the machine runs; verified source is what an author published. They can disagree, and unverified contracts only offer the former. Use both when both exist.
Can disassembly show whether a contract is a honeypot?
Sometimes patterns are visible, but this tool does not classify honeypots. Opaque bytecode and missing source are reasons for caution; the token safety page runs the structured sellability checks.