Date Range (Required)
The date range is the single biggest driver of export size. Wider ranges mean more rows, more GB, and higher credit cost.- Start with a single day or week for initial runs
- Use the “Current” button to set the end date to the present
- Supports datetime values for hourly precision
Wallet Address (Optional)
Filter results to activity involving specific wallet addresses.- Supports up to 500 addresses per job
- Useful for verifying output against known wallet activity
Token Address (Optional)
Filter to specific token contracts — for example, USDC or WETH. This is useful when you only need transfer or swap data for particular tokens rather than all activity on the chain.Field Selection
When creating an export, you can select specific fields from each dataset. More fields increase export size and GB consumption proportionally. Start with the minimum fields you actually need. You can always run additional exports with more fields later.Scoping Best Practices
| Approach | Impact |
|---|---|
| Narrow date range | Fewer rows, lower credit cost |
| Add wallet or token filter | Targets specific activity instead of full chain |
| Select fewer fields | Smaller file size per row |
| Combine all three | Minimal, focused export for validation |
You can run estimates as many times as you want at no cost. Use estimates to iterate on your filters before committing credits.