Ethereum Debug Methods
This section documents Ethereum's powerful debug API methods that provide advanced capabilities for blockchain analysis, transaction debugging, and detailed state inspection. These methods are essential for developers building sophisticated Ethereum applications, tools, and analytics.
Debug Methods Overview
Debug methods allow you to perform detailed analysis of blockchain data, trace transaction execution at the EVM level, inspect state changes, and diagnose issues with transactions or smart contracts. These advanced inspection capabilities are crucial for developers working on complex smart contracts or building analytical tools.
| Method Calls | HTTP! | WS! |
|---|---|---|
| debug_getBadBlocks Returns a list of the last 'bad blocks' that the client has seen on the network | ||
| debug_storageRangeAt Returns the storage range of a contract at a specific block height | ||
| debug_traceBlock Returns all traces created at a given block | ||
| debug_traceBlockByHash Returns all traces created at a block specified by its hash | ||
| debug_traceBlockByNumber Returns all traces created at a block specified by its number | ||
| debug_traceCall Executes a new message call and returns the traces created during execution | ||
| debug_traceTransaction Returns all traces of a given transaction | ||
The debug namespace provides methods for:
- Tracing transaction execution with granular control over tracing parameters
- Analyzing block execution with different trace types (e.g., call tracer, 4byte tracer)
- Inspecting contract storage and state
- Retrieving information about bad blocks
- Analyzing call and execution contexts
These methods typically provide more detailed output than standard API methods, making them valuable for deep debugging and analysis tasks.
See also
- All Available Methods - Complete Method Reference
- Core Methods - Essential API Functionality
- Trace Methods - Alternative Tracing Capabilities
- Development Guides - Practical Implementation Help