$> Kaya
~/tools/transaction-analyzerinteractive
/tools/transaction-analyzer

Transaction Analyzer

Use this transaction analyzer to inspect a raw signed EVM transaction and summarize fields like type, calldata bytes, fee model, and signature parts.

~/tools/transaction-analyzeranalyze evm tx
Transaction analysis
~/tools/transaction-analyzer/examplesusage.txt

Example Usage

  • Paste a signed raw transaction and inspect whether it is legacy or EIP-1559 style.
  • Check calldata size, zero bytes, and intrinsic gas assumptions quickly.
  • Review signature fields and fee settings before relaying a transaction elsewhere.
~/tools/transaction-analyzer/guideREADME.md

Transaction Analyzer Explained

A transaction analyzer helps you inspect a raw signed EVM transaction beyond simple field decoding. It summarizes chain context, gas settings, calldata size, zero and non-zero byte counts, intrinsic calldata gas, and signature parts in a compact view. That makes it useful when debugging signed payloads, checking fee model assumptions, or comparing how much calldata overhead a transaction carries. It is a good complement to a basic transaction decoder because it focuses on operational characteristics rather than only structural fields.

~/tools/transaction-analyzer/faq3 items

FAQ

How is this different from a transaction decoder?

A decoder focuses on the fields themselves, while this analyzer also summarizes byte-level and gas-related characteristics.

Does it support EIP-1559 transactions?

Yes. It can summarize legacy and typed transaction fee fields when present.

Why count zero and non-zero calldata bytes?

Because they affect intrinsic calldata gas cost on EVM chains.

~/tools/transaction-analyzer/related5 links
~/tools/transaction-analyzer/linksinternal