Skip to main content
POST
/
2fc1de7f08c0465f6a28e3c355e0cb14
Replay transactions in a block
curl --request POST \
  --url https://base-mainnet.core.chainstack.com/2fc1de7f08c0465f6a28e3c355e0cb14 \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "method": "trace_get",
  "params": [
    "0x1759c699e6e2b1f249fa0ed605c0de18998bc66556cd6ea3362f92f511aeb06a",
    [
      "0x0"
    ]
  ],
  "id": 1
}
'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": [
    {}
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt

Use this file to discover all available pages before exploring further.

Base API method trace_get retrieves a specific trace from a transaction by its index. This method is particularly useful for developers, auditors, and analysts who are interested in examining a particular step or operation within a transaction’s execution path. It allows for a focused analysis on a segment of the transaction’s trace, providing detailed information about a single operation, including calls to other contracts, state changes, and execution outcomes.

​
Parameters

  • transactionHash — The hash of the transaction from which you want to retrieve a trace, specified as a hexadecimal string.
  • traceIndex — An array of integers specifying the index of the trace to retrieve. The index reflects the order of operations within the transaction’s execution path.

​
Response

  • result — The trace data for the specified index within the transaction. This includes detailed information about the operation, such as the operation type, call data, value transferred, and the result of the operation. This focused trace can provide insights into specific actions taken by the transaction, including interactions with smart contracts and changes to the blockchain state.

​
Use case

The trace_get method is invaluable for detailed transaction analysis, especially when investigating complex transactions that involve multiple steps or interactions with various contracts. Developers can use it to debug specific operations within a transaction, auditors can employ it to verify the correctness and security of particular steps, and analysts might use it to study the behavior of contracts and transactions on a granular level.

Body

application/json
​
jsonrpc
string
default:2.0
Example:

"2.0"

​
method
string
default:trace_get
Example:

"trace_get"

​
params
array
Example:
[
  "0x1759c699e6e2b1f249fa0ed605c0de18998bc66556cd6ea3362f92f511aeb06a",
  ["0x0"]
]
​
id
integer
default:1
Example:

1

Response

200 - application/json

Trace data for transactions in the specified block

​
jsonrpc
string
​
id
integer
​
result
object[]
Last modified on May 18, 2026