Marketplace Market Share

Given a chain, get the market share in terms of USD transacting volume and number of trades for either dex or nft sector.

• Query can be found here
• Chains included are: all EVM chains on Dune
• Scheduled to update every day (23:30 UTC)
• You can apply filters like WHERE, IN, AND/OR upon results

Use Cases

• Recommend trending or emerging marketplaces by tracking shifts in the market share over time.
• Feed into a marketing ROI tracker to assess campaign impacts on marketplace market share.
• Build a competive analysis tool to monitor marketplaces and sectors’ market share over time.

Column Descriptions

Column	Description	Type
time	Date of the marketshare data	string
market	Sector identifier: ‘dex’ or ‘nft’	string
blockchain	The blockchain where the marketplace operates on	string
project	Specific DEX or NFT marketplace name	string
version	Contract version of the marketplace protocol, e.g. ‘v2’	string
volume_usd	USD volume traded on the marketplace	double
trades	Number of trades on the marketplace	int

Headers

X-Dune-Api-Key

string

required

API Key for the service

Path Parameters

market

string

required

Sector of the marketshare, either 'dex' or 'nft'

chain

string

required

Chain name (use Dune namespace, e.g. ethereum, solana, bnb, polygon, etc)

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

cancelled_at

string

Timestamp of when the query execution was cancelled, if applicable.

execution_ended_at

string

Timestamp of when the query execution ended.

execution_id

string

Unique identifier for the execution of the query.

execution_started_at

string

Timestamp of when the query execution started.

expires_at

string

Timestamp of when the query result expires.

is_execution_finished

boolean

Whether the state of the query execution is terminal. This can be used for polling purposes.

next_offset

integer

Offset that can be used to retrieve the next page of results.

next_uri

string

URI that can be used to fetch the next page of results.

query_id

integer

Unique identifier of the query.

result

object

The object containing the results and metadata of the query execution

Show child attributes

result.metadata

object

Metadata about the execution of the query, including details like column names, row counts, and execution times.

Show child attributes

result.metadata.column_names

string[]

Names of the columns in the result set.

result.metadata.column_types

string[]

Types of the columns in the result set.

result.metadata.datapoint_count

integer

Results cell count is used for billing/pricing plans here we expose the these values to the user, so that they can track their costs

result.metadata.execution_time_millis

integer

Time in milliseconds that the query took to execute.

result.metadata.pending_time_millis

integer

Time in milliseconds that the query was pending before execution.

result.metadata.result_set_bytes

integer

ResultSetBytes represents the raw data bytes returned by the SQL execution engine, it includes:

• total nr of bytes used on 1 line with all the column names (the header of the result set)
• total nr of bytes for all the row values (the result set of rows)

it doesn't include overheads such as the presence of column names for every row in the JSON result type. it also doesn't include opmitizations such as compression

result.metadata.row_count

integer

Number of rows in the result set for the current page of results.

result.metadata.total_result_set_bytes

integer

Total number of bytes in the result set. This doesn't include the json representation overhead.

result.metadata.total_row_count

integer

Number of rows in the result set for the entire result set.

result.rows

object[]

A list of rows. A row is dictionary of key-value pairs returned by the query, each pair corresponding to a column

Show child attributes

result.rows.{key}

object

state

string

The state of the query execution.

submitted_at

string

Timestamp of when the query was submitted.