POSTtrace_call
Simulates a specified transaction call and returns the result. This method does not actually send a transaction to the blockchain and provides detailed execution information including gas consumption, execution results, and logs. This is useful when you want to preview how a specific function call will be executed.
Enter the following parameters as an array with the appropriate types.
call objectis an object containing the following fields.trace type: Select one or more trace types to use and enter as an array. You can use "vmTrace", "trace", or "stateDiff" values. See the API documentation for details on each option.block number or block tag: Enter the block number in hexadecimal string format. You can also enter block tags such as "earliest", "latest", or "pending".
Enter the transaction's from address as a string.
Enter the transaction's to address as a string.
Enter the gas required to process the transaction as a hex-format string. For smart contract calls, no gas is consumed, so you can enter 0x0.
Enter the desired cost per gas as a hex-format string.
The value of the transaction.
The method signature hash of the transaction to execute. Can be referenced from the ABI.
Trace type specifies the data types used when querying detailed execution information for a specific transaction or block on the Ethereum blockchain. This array can contain the following three string values:
- vmTrace: Traces the virtual machine's step-by-step execution in detail. This includes memory state, stack state, and the result of each execution instruction.
trace: Provides step-by-step logs of transaction execution. These logs include call flow and details of internal transactions that occurred.stateDiff: Shows the difference in account state before and after transaction execution. This includes changed storage keys and values, account balance changes, and contract code changes.
This information helps developers better understand the transaction processing flow and debug. Each type provides detailed information on a specific aspect of the blockchain to clearly understand the impact of a transaction.
Enter the transaction's from address as a string.
Enter the transaction's to address as a string.
Enter the gas required to process the transaction as a hex-format string. For smart contract calls, no gas is consumed, so you can enter 0x0.
Enter the desired cost per gas as a hex-format string.
The value of the transaction.
The method signature hash of the transaction to execute. Can be referenced from the ABI.
Caller address
Call type (call, delegatecall, staticcall, etc.)
Gas limit set for the call (hex)
Call input data (hex)
Callee address
Amount of ETH transferred (hex, in wei)
Hash of the block containing this transaction
Block number containing the transaction
Actual gas used (hex)
Call return data (hex)
Number of sub-traces
Index array representing the trace path
Hash of the traced transaction
Position of the transaction within the block
Trace type (call, create, reward, etc.)