Skip to main content

Requirements

The examples in this guide call the debug JSON-RPC endpoints directly with curl — no SDK or additional libraries are required. Optionally install jq to pretty-print the JSON responses:
Debug tracing is your primary tool for understanding EVM transaction execution on Sei. This comprehensive system allows you to analyze transaction flow, optimize gas usage, debug smart contract interactions, and troubleshoot production issues.

What You Can Trace

Transaction Execution

  • Step-by-step opcode execution
  • Contract call hierarchy
  • Gas consumption breakdown
  • State changes and storage access

Contract Interactions

  • Cross-contract calls and returns
  • Event emission analysis
  • Precompile usage tracking
  • External library calls

Performance Analysis

  • Gas optimization opportunities
  • Bottleneck identification
  • Cache hit/miss patterns
  • State access efficiency

Security Analysis

  • Suspicious operation detection
  • Reentrancy pattern analysis
  • Access control verification
  • Vulnerability scanning

Available Tracing Methods

Transaction Analysis Example

Tracing an ERC-20 transfer transaction:
Response:

Debugging Failed Transactions

Steps to analyze and resolve transaction failures:

Step 1: Identify the Problem

Step 2: Trace the Execution

Response

Step 3: Fix and Test

Common Debugging Scenarios

Transaction Reverted

Problem: Transaction failed with revert Solution: Use callTracer to find the exact revert reason

Out of Gas

Problem: Transaction ran out of gas Solution: Use gas analysis tracer to optimize gas usage

Unexpected Behavior

Problem: Transaction succeeded but wrong result Solution: Use opcode tracer for step-by-step analysis

Slow Performance

Problem: Transaction uses too much gas Solution: Use state access tracer to find inefficiencies

Quick Reference

Essential Commands

Common Tracers

  • callTracer: Contract call hierarchy
  • opcodeTracer: Opcode-level execution
  • Custom JS: Custom analysis logic

Pre-Baked Trace Cache

RPC nodes can optionally pre-compute and cache debug_trace* results in the background so that trace requests are served from a local on-disk cache instead of re-executing the block live on every call. This is an opt-in feature configured through new [evm] fields in app.toml and is recommended for RPC nodes only. When enabled, a background worker re-executes each committed block with the configured tracers and stores the results in a Pebble database at <home>/data/trace_db. The following methods serve from this cache on hit, and otherwise fall through to live re-execution:
  • debug_traceTransaction
  • debug_traceBlockByNumber and debug_traceBlockByHash

When the cache is used

A request is only served from cache when trace baking is enabled and the request uses a bakeable tracer configuration:
  • The tracer is one of callTracer, prestateTracer, or flatCallTracer.
  • No custom tracerConfig is supplied. A per-call tracerConfig (for example {"withLog": true}) is not part of the cache key, so any custom tracer config makes the request un-bakeable and it falls through to live re-execution.
Requests that use the struct logger (no tracer), a JavaScript tracer, or any other named tracer are always executed live.

Configuration

Trace baking is controlled by these [evm] fields in app.toml:
Enabling trace baking adds a persistent on-disk store at <home>/data/trace_db and increases disk usage. The store’s write-ahead log is flushed when the node shuts down cleanly.

Removed legacy trace filters

The legacy *ExcludeTraceFail endpoints have been removed. Use debug_traceBlockByNumber or debug_traceBlockByHash for block tracing and eth_getTransactionReceipt for EVM receipts. There is no block or filter method for discovering synthetic logs from Cosmos-originated transactions. If you already know a synthetic transaction hash, enable sei_getTransactionReceipt to retrieve its receipt and logs.

Next Steps

  1. JavaScript Tracers - Custom analysis scripts
  2. Troubleshooting - Common issues and solutions
Start with callTracer for general debugging, then use specialized tracers for specific analysis needs.