DEX Pair Stats
Given a blockchain, retrieves essential metadata and statistical data for token pairs. Metadata encompasses all pool addresses associated with the token pair, the DEXs or projects where they are available, and their token addresses. Key statistics provided include one-day, seven-day, and thirty-day trading volumes, USD liquidity, and the seven-day volume-to-liquidity ratio.
- Query can be found here
- Chains included are:
arbitrum
,base
,bnb
,celo
,ethereum
,fantom
,gnosis
,optimism
,polygon
,scroll
,zk_sync
,solana
- Scheduled to update every 30 minutes
- You can apply filters like WHERE, IN, AND/OR upon results
- Each row is uniquely identified by the
chain
,token_a_address
, andtoken_b_address
columns combination.
Use Cases
- Enable DEX aggregators to identify all pools for swapping specific token pairs or addresses, using filters such as
filter='USDC-WETH'
orfilters=token_a_address = '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48' or token_b_address = '0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48'
. - Identify the token pair with the highest USD liquidity on a given chain by sorting results with
sort_by=usd_liquidity desc
. - Provide aggregated DEX pair statistics, including volume and liquidity, to algorithmic trading bots and risk management systems.
Column Descriptions
Column | Description | Type |
---|---|---|
chain | The blockchain where the token pair is traded | string |
token_pair | The identifier of the token pair, e.g., ‘USDC-WETH’ | string |
projects | List of DEX projects offering the token pair | array(string) |
pool_ids | Contract addresses of pools containing the token pair | array(string) |
token_a_address | Contract address of the first token in the pair | string |
token_b_address | Contract address of the second token in the pair | string |
one_day_volume | 24-hour USD trading volume for the token pair across all pools on all DEXes | double |
seven_day_volume | 7-day USD trading volume for the token pair across all pools on all DEXes | double |
thirty_day_volume | 30-day USD trading volume for the token pair across all pools on all DEXes | double |
all_time_volume | Total USD trading volume for the token pair since inception across all pools on all DEXes | double |
usd_liquidity | Current USD liquidity available in all pools for the token pair on all DEXes | double |
seven_day_volume_liquidity_ratio | 7-day trading volume to liquidity ratio for the token pair across all pools on all DEXes | double |
Headers
API Key for the service
Path Parameters
The blockchain where the token pair is traded
Query Parameters
API Key, alternative to using the HTTP header X-Dune-Api-Key
This enables returning a query result that was too large and only a partial result is available. By default allow_partial_results is set to false and a failed state is returned.
Specifies a comma-separated list of column names to return. If omitted, all columns are included. Tip: use this to limit the result to specific columns, reducing datapoints cost of the call.
Expression to filter out rows from the results to return. This expression is similar to a SQL WHERE clause. More details about it in the Filtering section of the doc. This parameter is incompatible with sample_count.
There is a default 250,000 datapoints limit to make sure you don't accidentally spend all your credits in one call. To ignore the max limit, you can add ignore_max_datapoints_per_request=true
Limit number of rows to return. This together with 'offset' allows easy pagination through results in an incremental and efficient way. This parameter is incompatible with sampling (sample_count).
Offset row number to start (inclusive, first row means offset=0) returning results from. This together with 'limit' allows easy pagination through results in an incremental and efficient way. This parameter is incompatible with sampling (sample_count).
Number of rows to return from the result by sampling the data. This is useful when you
want to get a uniform sample instead of the entire result. If the result has less
than the sample count, the entire result is returned. Note that this will return a
randomized sample, so not every call will return the same result. This parameter is
incompatible with offset
, limit
, and filters
parameters.
Expression to define the order in which the results should be returned. This expression is similar to a SQL ORDER BY clause. More details about it in the Sorting section of the doc.
Response
Timestamp of when the query execution was cancelled, if applicable.
Timestamp of when the query execution ended.
Unique identifier for the execution of the query.
Timestamp of when the query execution started.
Timestamp of when the query result expires.
Whether the state of the query execution is terminal. This can be used for polling purposes.
Offset that can be used to retrieve the next page of results.
URI that can be used to fetch the next page of results.
Unique identifier of the query.
The object containing the results and metadata of the query execution
The state of the query execution.
Timestamp of when the query was submitted.
Was this page helpful?