RPC errors · debug_traceTransaction

debug_traceTransaction: transaction not found / genesis is not traceable

What it means

Unlike -32601, these answers mean tracing is enabled: the node tried and could not trace this transaction. "transaction not found" means the hash is not in the node's transaction index, because it is wrong, not yet mined, on a different chain, or older than the index the node keeps. "genesis is not traceable" comes back when the lookup resolves to the genesis block, which has no parent state to replay from.

The exact messages, and where we saw them

Returned by real upstream nodes when we triggered this error on 2026-09-24 through our endpoint on each chain we serve.

transaction not found
Code -32001. Seen on 6 chains: Berachain, Boba Network, Katana, Optimism, Plasma, Taiko.
transaction not found
Code -32000. Seen on 5 chains: Arbitrum, Beam, Ethereum Classic, Ethereum, Shibarium.
genesis is not traceable
Code -32000. Seen on 2 chains: Scroll, WEMIX.

How to fix it

  • Confirm the hash with eth_getTransactionByHash on the same endpoint and chain first.
  • For old transactions, use a node with full transaction indexing (geth --history.transactions=0 or an archive node), since many nodes only index recent history.
  • Tracing also needs the parent block's state; a pruned node can find the transaction and still fail to replay it.

Related