---
title: "Exchange Fee Dominance"
method: GET
path: "/v1/metrics/fees/exchanges_relative"
---

# Exchange Fee Dominance

`GET /v1/metrics/fees/exchanges_relative`

**Definition.** Exchange Fee Dominance is the percentage of total transaction fees paid in transactions related to on-chain exchange activity, segmented by counterparty role:\n- Deposits: transactions that include an exchange address as the receiver of funds.\n- Withdrawals: transactions that include an exchange address as the sender of funds.\n- In-House: transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\n**Technical.** When a transaction can be categorized into multiple of these categories, for example a transaction that sends funds externally as well as in-house, the fees are split into percentages according to the volume transferred. Exchange metrics are based on Glassnode's continually updated set of labeled exchange addresses, together with statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as labels update. For methodology and limitations, see our [article on exchange metrics](https://insights.glassnode.com/exchange-metrics/) and [Exchange Data Transparency Notice](https://docs.glassnode.com/further-information/exchange-data-transparency-notice).\n

[View in Studio](https://studio.glassnode.com/charts/fees.ExchangesRelative?a=BTC)

## Query parameters

- `a` string, required
- `s` integer
- `u` integer
- `i` string
- `f` 'csv' | 'json'
- `timestamp_format` 'unix' | 'humanized'

## Response `200`

Successful response

- TimeSeriesDataPoint[]
  - `t` integer — Unix timestamp
  - `v` union — Metric value (can be number, object, or array depending on the metric)
    - number
    - object
  - `o` object — Object containing multiple metric values (when applicable)

## Other responses

- `400` — Bad Request - Invalid parameters or unsupported asset
- `401` — Unauthorized - Invalid or missing API key
- `429` — Too Many Requests - Rate limit exceeded

---

[API](https://skmtc.net/glassnode/apis/glassnode-api-addresses.md) · [All operations](https://skmtc.net/glassnode/apis/glassnode-api-addresses/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/glassnode/glassnode-api-addresses/versions/7f6a24031f46/schema)