Trades - All (V3)

Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

Filtered V3 trade feed across the whole chain.

limit supports 1 to 100 items per request, and offset + limit must stay within 10,000.
Solana notes:
- Transaction data includes signers — a list of accounts that authorize the transaction with their signatures.
- If time range and block number range are not provided:
  - If sort_by = block_unix_time, default to fetching swaps within the last 7 days.
  - If sort_by = block_number, default to fetching swaps within the last 500,000 blocks.
- Only one type of filter is accepted: either block time range or block number range.
- If filtering by block time (after_time, before_time), only allow sorting by block_unix_time.
- If filtering by block number (after_block_number, before_block_number), only allow sorting by block_number.
- Constraints:
  - Block time range cannot exceed 30 days.
  - Block number range cannot exceed 500,000 blocks.
  - If only after_time is provided with no before_time, it must be within the last 30 days.
  - If only after_block_number is provided with no before_block_number, it must be within the most recent 500,000 blocks.
If source is used, it is supported on Solana only.
sort_type is descending-only in V3 trade endpoints.

Compute Unit ⚙️

Use Cases 💡

Get recent DEX trades across all tokens and pairs on a specific chain.
Great for tracking whale activity, token movements, or suspicious patterns.
Build filtered chain-wide trade feeds across tokens, pools, owners, or DEX sources.
Investigate bursts of activity around a wallet, venue, or block range.
Power analytics pipelines that need raw trades beyond a single token or pair.
Detect chain-wide market flow patterns before summarizing them into dashboards or alerts.

How to Use 🛠️

Set x-chain for the target network.
Filter by tx_type, owner, pool_id, source, and either time range or block-number range.
Use sort_by=block_unix_time for time windows and sort_by=block_number for block windows.
Keep offset + limit <= 10000.

Best Practices ✅

Use block ranges when you care about precise chain progression and time ranges when you care about wall-clock windows.
Do not mix time and block filters in the same request; split them into separate jobs if needed.
On non-Solana chains, omit source and rely on other filters instead.

200JSON object containing trades