The eth_traces_v2_rpc table contains EVM transaction traces, including both main and internal transactions. Basically the same as eth_traces_rpc, but it uses another RPC interface: debug_traceBlockByNumber, which is a debugging API method provided by the Geth (Go-Ethereum) client.
Procedure
Establish a Connection: Connect to your Ethereum node using the URL provided in the inputs.
Set Block Range: Determine the block range by specifying fromBlock and toBlock. These arguments represent the starting and ending block numbers for scanning.
Execute RPC Call: Invoke the eth_traces_v2_rpc function, passing the required arguments (fromBlock, toBlock, and url).
Retrieve and Analyze Data: Collect the output data, which includes detailed transaction traces. Use this data to gain insights into transaction processes and perform any necessary debugging or analysis.
Inputs
Args
Types
Info
fromBlock
BigInt
Block number to start scanning from.
toBlock
BigInt
Block number to stop scanning at.
url
VARCHAR
URL of the Ethereum node.
Outputs
Column names
Types
Info
blockNumber
BIGINT
The block number.
type
VARCHAR
trace type.(CALL, STATICCALL, DELEGATECALL...)
from
VARCHAR
address of the sender
to
VARCHAR
address of the receiver
value
VARCHAR
Amount of ETH sent from sender to recipient (if any), measured in wei (1 ETH = 10^18 wei)
input
VARCHAR
call data provided to this trace, often containing function signatures and parameters
gas
BIGINT
gas provided by the caller
error
VARCHAR
Error message or code if the trace execution failed
output
VARCHAR
output data from the call.
gasUsed
BIGINT
Actual amount of gas consumed by this trace's execution
subtraces
BIGINT
Number of subtraces created by this trace
traceAddress
LIST(BIGINT)
Array indicating the exact position of this trace within the trace tree of the transaction