trace_transaction | BNB Chain

BNB API method that traces a specific transaction. It provides a detailed record of all the steps the Ethereum Virtual Machine (EVM) took during the execution, including all the operations performed and the changes made to the blockchain state. This method is available on Erigon only.

👍

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

Enable the Erigon client on your elastic Ethereum node

📘

Available on the Business subscription plan and higher.

Once you have joined a public network, do the following:

1. Select the project with the network.
2. Select the network.
3. Click Add node.
4. Provide a node name.
5. Under Type, select Elastic.
6. Under Mode, select Archive. With an archive node, you will be able to query historical states for the entire chain.
7. Under Debug and trace APIs, select On.
8. Under Hosting, select Chainstack.
9. For Chainstack hosting, select a cloud provider and a region.
10. Review your changes and click Add node.

Once deployed, the node status will change from Pending to Running. You will also see the Debug and trace tag next to the node name.

Enable the Erigon client on your dedicated Ethereum node

📘

Available on the Growth subscription plan and higher.

Once you have joined a public network, do the following:

1. Select the project with the network.
2. Select the network.
3. Click Add node.
4. Provide a node name.
5. Under Type, select Dedicated.
6. Under Mode, select Archive. With an archive node, you will be able to query historical states for the entire chain.
7. Under Hosting, select Chainstack. See Supported hosting options.
8. For Chainstack hosting, select a cloud provider and a region.
9. Under Client, select Erigon.
10. Review your changes and click Send request.

The Chainstack Sales team will reach out to your shortly.

Parameters

• hash — the hash identifying a transaction

Response

• action — an object that describes the action taken by the transaction:
  • from — the address of the sender who initiated the transaction.
  • callType — the type of call, call or delegatecall, two ways to invoke a function in a smart contract. call creates a new environment for the function to work in, so changes made in that function won't affect the environment where the function was called. delegatecall doesn't create a new environment. Instead, it runs the function within the environment of the caller, so changes made in that function will affect the caller's environment.
  • gas — the units of gas included in the transaction by the sender.
  • input — the optional input data sent with the transaction, usually used to interact with smart contracts.
  • to — the address of the recipient of the transaction if it was a transaction to an address. For contract creation transactions, this field is null.
  • value — the value of the native token transferred along with the transaction, in Wei.
  • blockHash — the hash of the block in which the transaction was included.
  • blockNumber — the number of the block in which the transaction was included.
  • error — a string that indicates whether the transaction was successful or not. null if successful, Reverted if not.
  • result — an object that contains additional data about the execution of the transaction:
    • gasUsed — the total used gas by the call, encoded as hexadecimal.
    • output — the return value of the call, encoded as a hexadecimal string.
  • subtraces — the number of sub-traces created during execution. When a transaction is executed on the EVM, it may trigger additional sub-executions, such as when a smart contract calls another smart contract or when an external account is accessed.
  • traceAddress — an array that indicates the position of the transaction in the trace.
  • transactionHash — the hash of the transaction.
  • transactionPosition — the position of the transaction in the block.
  • type — the type of action taken by the transaction, call or create. call is the most common type of trace and occurs when a smart contract invokes another contract's function. create represents the creation of a new smart contract. This type of trace occurs when a smart contract is deployed to the blockchain.

trace_transaction code examples

const { Web3, Web3PluginBase } = require("web3");
const NODE_URL = "CHAINSTACK_NODE_URL";
const web3 = new Web3(NODE_URL);

// Define the TraceBlockPlugin class
class TraceBlockPlugin extends Web3PluginBase {
    pluginNamespace = 'erigon';

    async traceTransaction(txHash) {
        return this.requestManager.send({
            method: 'trace_transaction',
            params: [txHash],
        });
    }
}

// Register the plugin
web3.registerPlugin(new TraceBlockPlugin());

async function traceTransaction(txHash) {
    const result = await web3.erigon.traceTransaction(txHash);
    console.log(result);
}

traceTransaction("0x0e77e2cf5a6999f616b56f1378b6c7b127b5a4e20cb2e12611d808af0979dacf");

const ethers = require('ethers');
const NODE_URL = "CHAINSTACK_NODE_URL";
const provider = new ethers.JsonRpcProvider(NODE_URL);

const traceTransaction = async (txHash) => {
  const traces = await provider.send("trace_transaction", [txHash]);
  console.log(traces);
};

traceTransaction("0x0e77e2cf5a6999f616b56f1378b6c7b127b5a4e20cb2e12611d808af0979dacf")

from web3 import Web3  
node_url = "CHAINSTACK_NODE_URL" 
web3 = Web3.HTTPProvider(node_url)

tx_hash = "0x0e77e2cf5a6999f616b56f1378b6c7b127b5a4e20cb2e12611d808af0979dacf"

traces = web3.provider.make_request('trace_transaction', [tx_hash])
print(traces)

Use case

A practical use case of the trace_transaction method can inspect NFT transfers, allowing you to identify internal transactions, the sender and receiver, and the amounts transferred. This can be especially useful when analyzing an ERC-721 token purchase on a marketplace like Opensea, where funds transfer is not always straightforward due to multiple internal calls for transferring funds to the NFT owner, paying royalties to the creator, and other factors. By using trace_transaction, you can gain a more comprehensive understanding of the transaction flow.

Try the trace_transaction RPC method yourself