> For the complete documentation index, see [llms.txt](https://dasus.gitbook.io/dasus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dasus.gitbook.io/dasus-docs/market-data-and-research/analytics.md).

# Analytics

**Analytics** is the market's own report card: where Hyperliquid stands right now and how it got here — volume, open interest, users, trades, liquidations and capital flows. It lives at `/overview` (navbar → **More** → **Analytics**), is read-only and needs no wallet.

Every chart names its source underneath. That is deliberate: some series are published by the protocol, some are measured by Dasus, and some come from a third party — and they do not all cover the same dates.

## Today

Four cards summarise the last 24 hours:

| Card                 | What it counts                                                                                       |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| **Perp volume 24h**  | Traded notional across the main perp book, with the number of markets                                |
| **HIP-3 volume 24h** | The same for the third-party perp dexes (stocks, indices, FX, commodities), with the number of dexes |
| **Spot volume 24h**  | Traded notional on the spot book                                                                     |
| **Open interest**    | Total size of open perp positions right now                                                          |

## By coin

Four charts break the market down market by market, so you can see which coins actually carry the activity:

* **Volume by coin** — stacked, so the share of each market is visible.
* **Open interest by coin**
* **Funding by coin** — hourly funding rate; see [Funding Rate](https://dasus.gitbook.io/dasus-docs/trading-concepts/funding-rate.md).
* **Unique traders by coin** — distinct accounts that traded it.

## Users and activity

* **Trades** — each day split into **taker** and **maker**, with the running total as a line.
* **Daily active users** — distinct accounts that traded.
* **New accounts** — accounts created each day, with the cumulative curve.

{% hint style="info" %}
**Active users are averaged, never summed.** When you group the daily-active series by week, month or year, the chart shows the **daily average** of the period. Adding the days together would count anyone who trades on several days once per day — a number that looks impressive and means nothing.
{% endhint %}

## Liquidations and flows

* **Capital in and out** — deposits (green) and withdrawals (red) each day, with the net running total.
* **Liquidations** — notional liquidated each day, split into **cross** and **isolated** margin. See [Liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md).

## All time

Cumulative totals since day one — total users, cumulative volume, trades and net capital in — plus a table of the **largest accounts by volume**.

## Reading the charts

Each chart carries the same controls: **Line**, **Area** or **Bars**; a range of **1M**, **3M**, **1Y** or **All**; and grouping by **day, week, month or year**.

## Where the data comes from, and the gap

{% hint style="warning" %}
**There is a hole in the history, and it is not a bug.** The protocol published its own statistics until **3 April 2026** and has not updated them since, so the volume, users and trades series stop there. Dasus began measuring the same figures itself every 15 minutes on **8 September 2026**. Between those two dates nobody was recording, and the charts show that gap rather than interpolating across it.
{% endhint %}

| Series                             | Source                                                 |
| ---------------------------------- | ------------------------------------------------------ |
| Volume, users, trades (historical) | HyperCore's published statistics, through 3 April 2026 |
| Everything after 8 September 2026  | Measured by Dasus every 15 minutes                     |
| Live cards and by-coin charts      | Hyperliquid's live market data                         |
| DEX volume and chain TVL           | DefiLlama, current, fetched by your browser            |

A series with too little history says so (*"Not enough history yet"*) instead of drawing a line through two points.

## Related pages

* [Markets](https://dasus.gitbook.io/dasus-docs/market-data-and-research/markets.md) — the catalogue behind these numbers
* [Heatmap](https://dasus.gitbook.io/dasus-docs/market-data-and-research/heatmap.md) — the same activity as a treemap
* [Perp Screener](https://dasus.gitbook.io/dasus-docs/market-data-and-research/screener.md) — per-market funding, open interest and liquidity
* [Whale Radar](https://dasus.gitbook.io/dasus-docs/market-data-and-research/whale-radar.md) — who is holding the open interest


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dasus.gitbook.io/dasus-docs/market-data-and-research/analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
