debug_traceBlockByNumber
Retrieves detailed execution information about transactions within a given block number. This is similar to trace_block.
Parameters
Quantity
ortag
- choose 1 of the following options:A hexadecimal block number.
"earliest"
- the earliest/genesis block."latest"
- the latest mined block."safe"
- the latest safe head block."finalized"
- the latest finalized block."pending"
- the pending state/transactions.
Tracer
- choose from one of these options:4byteTracer
- Solidity contract functions are addressed using the first four byte of the Keccak-256 hash of their signature. Thistracer
monitors and analyzes the usage of specific function signatures within smart contracts by capturing their unique first four bytes.callTracer
- collects data about all call frames executed within a transaction, creating a hierarchical list of call frames structured mirroring the EVM's operations. This is useful for debugging and analytical purposes.prestateTracer
- captures and analyzes the state of the blockchain before the execution of a specific transaction. It helps in understanding the state changes and effects that a transaction will have on the blockchain's data and accounts before the transaction is actually executed.noopTracer
- returns empty results. This is used for testing purpose.opcountTracer
- count and track the number of operations (or opcodes) executed during a specific transaction.unigramTracer
- counts the frequency of occurrence of each opcode.bigramTracer
- a bigram refers to a sequence of two bytes or characters. This tracer is designed to observe and provide insights into the patterns and occurrences of these two-byte sequences as they appear within the data of executed transactions.trigramTracer
- a trigram refers to a sequence of three bytes or characters. This tracer is designed to observe and provide insights into the patterns and occurrences of these three-byte sequences as they appear within the data of executed transactions.evmdisTracer
- generates the bytecode disassembly of executed transactions, providing developers with insights into how smart contracts operate at a low-level bytecode level for debugging, security audits, and performance optimization purposes.
Sample Request
curl https://lb.nodies.app/v1/<INSERT URL> \
-H "x-api-key: <API-KEY>" \
-X POST \
-H "Content-Type: application/json" \
-d '{
"method": "debug_traceBlockByNumber",
"params": [
"0x2973e",
{
"tracer": "callTracer"
}
],
"id": 1,
"jsonrpc": "2.0"
}'
Sample Response
{
"jsonrpc": "2.0",
"id": 1,
"result": [
{
"result": {
"from": "0x50b8f981ce93fd5b81b844409169148428400bf3",
"gas": "0x74448",
"gasUsed": "0x14cfe",
"to": "0x672e330b81a6d6c4fb2a7cad28b3f2295efaab77",
"input": "0xd5064ed1000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000000015553445f45544800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000004c600000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000014f856bf34f",
"value": "0x1",
"type": "CALL"
}
}
]
}
Last updated