API Reference
SupportStatusSign UpLogin

trace_block - Kaia

post
https://{kaia-network}.gateway.tatum.io/

The trace_block is a JSON-RPC method that allows you to fetch the trace details for a given block based on the block height. This method can be useful when you need detailed trace information for a specific block.

Use cases for this method may include:

  • Analyzing the internal operations of transactions within a block
  • Debugging smart contract interactions
  • Collecting data for in-depth blockchain analytics
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
integer
Defaults to 1
string
Defaults to 2.0
string
Defaults to trace_block
params
array of strings
length between 1 and 1
Defaults to latest

Array of HEX String.
The following options are possible for the defaultBlock parameter.

  • An integer block number (in hex)
  • String 'earliest' for the earliest/genesis block. String 'latest' - for the latest mined block. String 'pending' - for the pending state/transactions.
params

String - Either the hex value of a block number OR block tags:

  1. block number (in hex) OR
  2. block tag (one of the following): * pending (Not available on Ethereum) - A sample next block built by the client on top of latest and containing the set of transactions usually taken from local mempool. Intuitively, you can think of these as blocks that have not been mined yet. * latest - The most recent block in the canonical chain observed by the client, this block may be re-orged out of the canonical chain even under healthy/normal conditions. * safe - The most recent crypto-economically secure block, cannot be re-orged outside of manual intervention driven by community coordination. Intuitively, this block is “unlikely” to be re-orged. * finalized - The most recent crypto-economically secure block, that has been accepted by >2/3 of validators. Cannot be re-orged outside of manual intervention driven by community coordination. Intuitively, this block is very unlikely to be re-orged. * earliest - The lowest numbered block the client has available. Intuitively, you can think of this as the first block created.

Response

Updated 11 days ago

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 11 days ago