curl --request POST \
--url https://optimism-mainnet.core.chainstack.com/efb0a5eccd2caa5135eb54eba6f7f300 \
--header 'Content-Type: application/json' \
--data '
{
"jsonrpc": "2.0",
"method": "debug_traceBlockByNumber",
"id": 1,
"params": [
"0x6eee7bc"
]
}
'{
"jsonrpc": "<string>",
"id": 123,
"result": [
{}
]
}curl --request POST \
--url https://optimism-mainnet.core.chainstack.com/efb0a5eccd2caa5135eb54eba6f7f300 \
--header 'Content-Type: application/json' \
--data '
{
"jsonrpc": "2.0",
"method": "debug_traceBlockByNumber",
"id": 1,
"params": [
"0x6eee7bc"
]
}
'{
"jsonrpc": "<string>",
"id": 123,
"result": [
{}
]
}debug_traceBlockByNumber RPC method is used to retrieve detailed execution traces for all transactions included in a block, identified by the block’s number. This method is particularly useful for developers and analysts who need to deeply understand transaction execution and state changes within a specific block.
debug_traceBlockByNumber, send a POST request with a JSON RPC call in the body.
string): The number of the block for which to retrieve the execution traces, in hexadecimal format.array): An array of execution traces for each transaction in the block. Each trace provides comprehensive details about the execution, including calls, state changes, and gas usage.debug_traceBlockByNumber method is essential for:
Was this page helpful?