debug_traceBlockByNumber - Mantle

Example code for the debug_traceBlockByNumber JSON-RPC method. Complete guide on how to use debug_traceBlockByNumber JSON-RPC in GetBlock Web3 documentation.

This method traces the execution of all transactions within a block specified by block number on the Mantle network. This is a premium method available on Mantle Sepolia Testnet.

Parameters

Parameter
Type
Description

blockNumber

string

Block number in hex, or "latest", "earliest"

traceOptions

object

(optional) Tracing options

Trace Options:

Field
Type
Description

tracer

string

Tracer type: "callTracer", "prestateTracer"

timeout

string

Timeout for the trace

tracerConfig

object

Configuration for the tracer

Request examples

curl
curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "debug_traceBlockByNumber",
    "params": ["0x3F6777", {"tracer": "callTracer", "timeout": "5s"}],
    "id": "getblock.io"
}'

Response

Response Parameters

Field
Type
Description

txHash

string

Transaction hash

result

object

Trace result for the transaction

type

string

Call type (CALL, DELEGATECALL, etc.)

from

string

Sender address

to

string

Recipient address

gasUsed

string

Gas used

Use Case

The debug_traceBlockByNumber method is essential for:

  • Sequential block analysis

  • Historical block tracing

  • Gas profiling over block ranges

  • Chain state debugging

  • Protocol monitoring

  • Block indexing with traces

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid ACCESS-TOKEN

-32602

Invalid params

Invalid block number

-32000

Block not found

Block does not exist

Web3 Integration

Last updated

Was this helpful?