debug_traceTransaction - Mantle

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

This method returns a full trace of a transaction execution. It allows developers to debug and analyze transaction behavior at the EVM level.

Parameters

Parameter
Type
Description

transactionHash

string

Hash of the transaction to trace

tracerConfig

object

(optional) Tracer configuration options

Tracer Config Options:

Field
Type
Description

tracer

string

Type of tracer ("callTracer" or "prestateTracer")

timeout

string

Timeout for the trace operation

onlyTopCall

boolean

Only trace the main call, not sub-calls

Request

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

Response

Response Parameters

Field
Type
Description

type

string

Call type (CALL, DELEGATECALL, etc.)

from

string

Sender address

to

string

Recipient address

value

string

Value transferred (hex)

gas

string

Gas provided (hex)

gasUsed

string

Gas used (hex)

input

string

Call input data

output

string

Call output data

calls

array

Sub-calls made during execution

Use Case

The debug_traceTransaction method is essential for:

  • Transaction debugging and analysis

  • Smart contract debugging

  • Gas optimization analysis

  • Understanding internal calls

  • Security auditing

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid ACCESS-TOKEN

-32000

Transaction not found

Invalid transaction hash

Web3 Integration

Last updated

Was this helpful?