Indexed Fields Reference for where and orderBy
Use indexed fields in your where filters and orderBy clauses. Filtering or sorting on non-indexed fields can lead to slow queries, timeouts.
This page lists the fields that are indexed for each cube, dataset, and chain type. Prefer these fields when building where and orderBy conditions.
In where, filter on at least one indexed field (Index 1, 2, 3, or 4 where applicable). In orderBy, sort by an indexed field when possible.
EVM (Archive)
| Cube | Index 1 | Index 2 | Index 3 | Index 4 |
|---|---|---|---|---|
| Balances | Balance_Address | Currency_SmartContract | — | — |
| Blocks | Block_Hash | Block_Number | — | — |
| Calls | Call_From | Call_To | Transaction_Hash | — |
| DEXTrades | Transaction_Hash | — | — | — |
| DEXTradeByTokens | Trade_Currency_SmartContract | Trade_Side_Seller | — | — |
| Events | Call_To | Transaction_Hash | — | — |
| MinerRewards | Block_Coinbase | Block_Number | Block_Hash | — |
| Holders | Currency_SmartContract | — | — | — |
| Transactions | Transaction_From | Transaction_Hash | Transaction_To | — |
| Transfers | Transaction_Hash | Transfer_Sender | Transfer_Receiver | Transfer_Currency_SmartContract |
Tron (Archive)
| Cube | Index 1 | Index 2 | Index 3 | Index 4 |
|---|---|---|---|---|
| Balances | Balance_Address | Currency_SmartContract | — | — |
| Blocks | Block_Hash | Block_Number | — | — |
| Calls | Call_From | Call_To | Transaction_Hash | — |
| DEXTrades | Transaction_Hash | — | — | — |
| DEXTradeByTokens | Trade_Currency_SmartContract | Trade_Side_Seller | — | — |
| Events | Call_To | Transaction_Hash | — | — |
| Holders | Currency_SmartContract | — | — | — |
| Transactions | Transaction_Hash | — | — | — |
| Transfers | Transaction_Hash | Transfer_Sender | Transfer_Receiver | Transfer_Currency_SmartContract |
Solana
Solana Realtime
| Cube | Index 1 | Index 2 | Index 3 |
|---|---|---|---|
| DEXPools | Pool_Market_MarketAddress | — | — |
| DEXTradeByTokens | Trade_Currency_MintAddress | — | — |
| Instructions | Transaction_Signer | Instruction_Program_Address | — |
| Transfers | Transfer_Receiver_Owner | Transfer_Sender_Owner | Transaction_Signature |
Solana Archive
| Cube | Index 1 | Index 2 | Index 3 |
|---|---|---|---|
| DEXTradeByTokens | Trade_Currency_MintAddress | Trade_Account_Owner | — |
Trading (Realtime)
| Cube | Index 1 | Index 2 | Index 3 | Index 4 | Index 5 |
|---|---|---|---|---|---|
| Currencies | Currency_Id | Interval_Time_Start | — | — | — |
| Tokens | Token_Id | Interval_Time_Start | Currency_Id | Token_Address | — |
| Pairs | Token_Id | Currency_Id | Interval_Time_Start | Token_Address | Pool_Address |
| Trades | Trader_Address | Pair_Token_Address | Pair_Pool_Address | — | — |
How to use this reference
- Identify your cube — e.g.
EVM.Transactions,Solana.Transfers,Trading.Tokens. - Check chain and dataset — EVM Archive, Tron Archive, Solana Realtime/Archive, or Trading Realtime.
- Use indexed fields in
where— Prefer filters on the indexed columns (Index 1, 2, 3, 4). Example: forEVM(dataset: archive).Transactions, filter onTransaction_From,Transaction_Hash, orTransaction_To. - Use indexed fields in
orderBy— Sort by one of the indexed fields (e.g.Block_Number,Transaction_Hash) for predictable, fast ordering.
Using fields that are not in these tables for filtering or sorting may work in some cases but can cause poor performance or unexpected behavior. When in doubt, stick to the indexed fields listed above.
Ready to run this in production?
Get an API key and run these queries in minutes, or talk to us about plans and enterprise delivery.