$> Kaya
~/tools/contract-bytecode-analyzerinteractive
/tools/contract-bytecode-analyzer

Contract Bytecode Analyzer

Use this contract bytecode analyzer to inspect a contract bytecode hex string, measure code size, detect common metadata patterns, and compare the size against EIP-170 limits.

~/tools/contract-bytecode-analyzeranalyze bytecode
Bytecode analysis
~/tools/contract-bytecode-analyzer/examplesusage.txt

Example Usage

  • Measure whether runtime or creation bytecode is close to the EIP-170 contract size limit.
  • Check whether a bytecode blob appears to contain Solidity metadata.
  • Inspect byte prefixes and suffixes when comparing contract build outputs.
~/tools/contract-bytecode-analyzer/guideREADME.md

Contract Bytecode Analyzer Explained

A contract bytecode analyzer helps you inspect the structure and size of an EVM bytecode blob before deployment or during debugging. By pasting the bytecode, you can quickly see how many bytes it contains, how many 32-byte words it spans, whether it appears to include metadata, and how close it is to the EIP-170 contract size limit. This is useful when optimizing contract builds, comparing compiler outputs, reviewing deployment artifacts, or checking whether a code sample is runtime bytecode or something larger. It gives you fast feedback without opening a full development environment.

~/tools/contract-bytecode-analyzer/faq3 items

FAQ

What is EIP-170?

EIP-170 sets a maximum size for deployed contract runtime bytecode on Ethereum.

Does metadata count toward contract size?

Yes. Metadata bytes are part of the bytecode length unless removed before deployment.

Can this tool prove whether bytecode is creation code or runtime code?

Not with full certainty, but it can provide size hints and patterns that help you inspect the blob more quickly.

~/tools/contract-bytecode-analyzer/related5 links
~/tools/contract-bytecode-analyzer/linksinternal