I'm using the disassembler from go-ethereum repo which fails on about 20% of the bytecode from the blockchain with missing/unknown opcodes. The disassembler on Etherscan fails as well.

Is there an up-to-date disassembler with complete opcode tables that can be used? Am I doing something wrong?

Examples of failed disassembly -

  1. 0x52ecf69544784165101e76a682eeea642e72584d
  2. 0x4432979c7c6bdd19f9ef20787c4ac9cc9710667b
  • It looks like whatever disassembler etherscan was using got fixed? If you click the "Switch To Opcodes View" button/link, it shows you a disassembly.
    – Jamie Hale
    Jun 22 '16 at 15:53

I've written another disassembler to help me understand some of this stuff, and because I really wanted offsets beside the instructions. You can find it here.


  • 3
    Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
    – Afr
    Jun 23 '16 at 6:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.