POST
/
365cf697a3ad6d950b4c4a911e2e4f4d
curl --request POST \
  --url https://starknet-mainnet.core.chainstack.com/365cf697a3ad6d950b4c4a911e2e4f4d \
  --header 'Content-Type: application/json' \
  --data '{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "starknet_traceBlockTransactions",
  "params": {
    "block_id": {
      "block_number": 456600
    }
  }
}'

Starknet OpenRPC spec

For the latest version of the publicly maintained OpenRPC spec, see the Starknet specs GitHub repo.

Starknet API method that returns the execution trace of all transactions in a given block.

It provides a detailed execution trace for each transaction in the specified block. This can be useful for debugging and analysis purposes, as it allows developers to see the exact sequence of operations that were performed during the execution of each transaction.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • block_id — the hash of the requested block, or number (height) of the requested block, or a block tag:

    • block_hash — hash of the block.
    • block_number — block number, accept integer.
    • block_tag — latest for the latest one added to the chain or pending for the pending one.

​
Response

  • result — the execution trace of all transactions in the block, represented as a list of transaction traces.

​
Use case

A practical use case for starknet_traceBlockTransactions is to analyze the execution of transactions in a specific block. This can be useful for debugging purposes, as it allows developers to understand the sequence of operations that were performed during the execution of each transaction.

​
Deprecated feeder gateway method

The feeder gateway was deprecated on December 11, 2023.

Example of the call you had to make to the feeder gateway before the deprecation:

Shell
curl 'https://alpha-mainnet.starknet.io/feeder_gateway/get_block_traces?blockNumber=456600'

Body

application/json

Response

200

Successful response