Skip to main content
GET
Get Transaction Traces
Supported chains: ethereum, polygon, base, arbitrum, optimism, binance, avalanche, gnosis
Per-chain trace fields: On arbitrum, avalanche, base, and optimism, the fields call_type, subtraces, balance, refund_address, author, reward_type, and init are always null — the underlying trace data does not carry them.
Pass the optional block_number query parameter whenever you know it — it makes the lookup significantly faster, especially on high-volume chains.
Polygon Data Availability: Polygon traces are only available from January 2025 onwards.

Authorizations

apikey
string
header
required

API key for authentication

Path Parameters

chain
enum<string>
required

The blockchain network to query

Available options:
ethereum,
polygon,
base,
arbitrum,
optimism,
binance,
avalanche,
gnosis
Example:

"polygon"

transaction_hash
string
required

Transaction hash (66 character hex string starting with 0x)

Pattern: ^0x[a-fA-F0-9]{64}$
Example:

"0x00dcc066aad65ae4f10c0fc4ec1fac5d3693c12c01d98a9f6a87448be9b26200"

Query Parameters

block_number
integer

Block number of the transaction. Optional but strongly recommended — providing it makes the lookup significantly faster, especially on high-volume chains.

Required range: x >= 0
limit
integer
default:10

Maximum number of results (1-50)

Required range: 1 <= x <= 50
offset
integer
default:0

Number of results to skip for pagination

Required range: x >= 0

Response

Transaction traces

transaction_hash
string
offset
integer
limit
integer
result
object[]
count
integer