debug_traceBlockByHash - Mantle

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

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

Parameters

Parameter
Type
Description

blockHash

string

32-byte block hash

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

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '
    "jsonrpc": "2.0",
    "method": "debug_traceBlockByHash",
    "params": [
        "0x9b14d73f45c836bfb0e1f59453c39fe8cddab45a0f78670dc6190e5c85b65a8e",
        {"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_traceBlockByHash method is essential for:

  • Block-level transaction analysis

  • MEV detection and analysis

  • Gas profiling across all block transactions

  • Security auditing of block activity

  • Chain forensics

  • Protocol debugging

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid ACCESS-TOKEN

-32602

Invalid params

Invalid block hash

-32000

Block not found

Block does not exist

Web3 Integration

Last updated

Was this helpful?