GET
/
v1
/
trends
/
evm
/
contracts
/
{chain}
curl --request GET \
  --url https://api.dune.com/api/v1/trends/evm/contracts/{chain} \
  --header 'X-Dune-Api-Key: <x-dune-api-key>'
{
  "cancelled_at": "2024-12-20T11:04:18.724658237Z",
  "execution_ended_at": "2024-12-20T11:04:18.724658237Z",
  "execution_id": "01HKZJ2683PHF9Q9PHHQ8FW4Q1",
  "execution_started_at": "2024-12-20T11:04:18.724658237Z",
  "expires_at": "2024-12-20T11:04:18.724658237Z",
  "is_execution_finished": true,
  "next_offset": 100,
  "next_uri": "https://api.dune.com/api/v1/execution/01HKZJ2683PHF9Q9PHHQ8FW4Q1/results?offset=100&limit=100",
  "query_id": 1234,
  "result": {
    "metadata": {
      "column_names": [
        "Rank",
        "Project",
        "Volume"
      ],
      "column_types": [
        "double",
        "varchar",
        "bigint"
      ],
      "datapoint_count": 1000,
      "execution_time_millis": 1000,
      "pending_time_millis": 1000,
      "result_set_bytes": 1000,
      "row_count": 10,
      "total_result_set_bytes": 10000,
      "total_row_count": 1000
    },
    "rows": [
      {}
    ]
  },
  "state": "QUERY_STATE_COMPLETED",
  "submitted_at": "2024-12-20T11:04:18.724658237Z"
}
  • Query can be found here
  • Scheduled to update once a day (12am UTC)
  • You can apply filters like WHERE, IN, AND/OR upon results

​
Use Cases

  • Feed into a CRM of developers and projects based on contract popularity
  • Build an explorer page of top trending contracts, with basic metadata to support.
  • Track trending contracts by value and type (user facing, contract facing, token, router, safes, etc.)

​
Column Descriptions

Column NameDescriptionType
contract_addressContract address of the contractstring
blockchainBlockchain of the contractstring
deployerDeployer address of the contractstring
contract_projectProject of the contractstring
contract_nameName of the contractstring
created_timeTime when the contract was createdstring
deployed_days_agoNumber of days since deploymentinteger
token_standardStandard of the token (ERC20,ERC721,ERC1155) if applicablestring
usd_value_receivedValue received in USD in ETH and ERC20 tokens in last 30 daysinteger
transaction_callsNumber of transaction calls (top level transactions) in last 30 daysinteger
unique_callersNumber of unique callers (tx from) in last 30 daysinteger
contract_callsNumber of calls from other contracts in last 30 daysinteger
unique_contract_callersNumber of unique contracts calling this contract in traces in last 30 daysinteger

Headers

​
X-Dune-Api-Key
string
required

API Key for the service

Path Parameters

​
chain
string
required

The blockchain where the token pair is traded

Query Parameters

​
api_key
string

API Key, alternative to using the HTTP header X-Dune-Api-Key

​
allow_partial_results
boolean

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.

​
columns
string

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.

​
filters
string

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.

​
ignore_max_datapoints_per_request
boolean

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
integer

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
integer

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).

​
queryID
integer
required
​
sample_count
integer

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.

​
sort_by
string

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

200
application/json
OK

The response is of type object.