The debug API methods allow you to inspect and debug the network. Infura supports the following debug methods on the Linea network:
Debug tracing types
The debug methods support the
prestateTracer tracing types, which return different results when specified
in the supported debug methods.
callTracer tracing type tracks all the call frames executed during a transaction, including the initial call. It returns a nested list of call frames, resembling how the EVM works. They form a tree with the top-level call at root
and sub-calls as children of the higher levels.
callTracer type returns an object with the following results:
|The type of call.
|The address the transaction is sent from.
|The address the transaction is directed to.
|The amount transferred in the call (hex-encoded).
|The amount of gas provided for the call (hex-encoded).
|The amount of gas used by the call (hex-encoded).
|The call data.
|The return data.
|If an error occurred during the call, this field will contain the error message.
|If the contract execution was reverted, this field will contain the reason for the revert (if provided by Solidity).
|Sub-calls made by the contract during the execution of the transaction.
prestateTracer tracing type records and tracks every change made to the state during the execution of transactions. It
generates an object that contains keys representing the addresses of the accounts involved in the transactions. The
corresponding values are objects that include specific fields related to the state changes made during the transaction:
|The account balance.
|The nonce value for the transaction.
|The hex-encoded bytecode.
|The storage slots of the contract.