Last updated
Last updated
Blockhash
- the hash of the block to be traced.
Tracer
- choose from one of these options:
4byteTracer
- Solidity contract functions are using the first four byte of the Keccak-256 hash of their signature. This tracer
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.
Retrieves detailed execution information about transactions within a given block hash.