> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# trace_transaction | BNB Chain

> BNB API method that traces a specific transaction. trace_transaction JSON-RPC method available on the BNB Chain blockchain via Chainstack.

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.

## 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

<CodeGroup>
  ```javascript ethers.js theme={"system"}
  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")
  ```

  ```python web3.py theme={"system"}
  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)
  ```
</CodeGroup>

## 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.


## OpenAPI

````yaml openapi/bnb_node_api/trace_transaction.json POST /35848e183f3e3303c8cfeacbea831cab
openapi: 3.0.0
info:
  title: BNB Node API
  version: 1.0.0
  description: This is an API for interacting with an BNB node.
servers:
  - url: https://bsc-mainnet.core.chainstack.com
security: []
paths:
  /35848e183f3e3303c8cfeacbea831cab:
    post:
      tags:
        - upload
      summary: trace_transaction
      operationId: trace_transaction
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                id:
                  type: integer
                  default: 1
                jsonrpc:
                  type: string
                  default: '2.0'
                method:
                  type: string
                  default: trace_transaction
                params:
                  type: array
                  items:
                    anyOf:
                      - type: string
                        title: Transaction hash
                        description: The hash of the transaction to trace.
                  default:
                    - >-
                      0x0e77e2cf5a6999f616b56f1378b6c7b127b5a4e20cb2e12611d808af0979dacf
      responses:
        '200':
          description: The transaction's trace.
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                  id:
                    type: integer
                  result:
                    type: object

````