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

# Traces Support Expands Across EVM Chains

*Published June 4, 2026*

![Traces Support Expands Across EVM Chains](https://www.datocms-assets.com/86369/1781068724-goldrush-traces-support.jpg)

The Foundational API now returns decoded EVM traces (internal transactions) for any wallet on supported chains. Add the `with-internal` query param and internal transfers come back flattened and attached to each transaction item, with from\_address, to\_address, value (in wei), and gas\_limit.

## What traces are for

Traces aren’t stored on-chain. They exist only as side effects of a parent transaction’s execution, and reconstructing them requires re-executing against an archive node. Use traces when you need:

* Native token movement triggered by contracts, like a router forwarding ETH to a recipient.
* DEX, lending, and bridge flows, where the EOA-visible to\_address is a contract rather than the ultimate recipient.
* Wallet balance reconciliation and tax reporting. Native-token deltas often can’t be explained from external transactions alone.
* Failed sub-calls within a multi-step transaction that still consumed gas.

## GoldRush endpoints with trace support

Add `with-internal=true` to:

* Get a transaction
* Get earliest transactions for address (v3)
* Get recent transactions for address (v3)
* Get paginated transactions for address (v3)

Internal transfers cost `0.05` credits per item on supported chains.

## Supported chains

Launch with support for: ApeChain, Arbitrum, Avalanche C-Chain, Base, Berachain, BNB Smart Chain (BSC), Ethereum, Gnosis, Linea, Mantle, Optimism, Plasma, Polygon, Taiko, Unichain, and World Chain.

[Learn more](https://goldrush.dev/docs/resources/traces-support)