> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/features/heatmap.md).

# Heatmap

Quickly see how the market is looking on the last 24 hours

<figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2FkCRtp1TxGGha045hdkha%2Fimage.png?alt=media&amp;token=e3bab5ef-fc06-4e7a-93d5-f86cba410875" alt="Heatmap treemap showing crypto market performance by size and color."><figcaption><p>Heatmap treemap showing crypto market performance by size and color.</p></figcaption></figure>

Use Proliquid Heatmap to scan crypto market performance by exchange, volume, or open interest and quickly find the strongest or weakest markets.

Each tile represents a market. Tile size can be grouped by volume or open interest, and color is based on the 24-hour percentage change. Green tiles are outperforming; red tiles are underperforming.

Use Heatmap to spot outliers:

* Strong markets on a red day.
* Weak markets on a green day.
* High-volume names absorbing or leading a move.
* Sectors where many related markets are moving together.

You can select Hyperliquid, RISEx, Lighter, Binance, Bybit, OKX, and Blofin.

## What the data means

| Metric                     | What it means                                                           | What to check next                                                                                                   |
| -------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Tile size by volume        | Larger tiles traded more notional value.                                | Use [Screener](/features/crypto-screener-for-hyperliquid-traders.md) to confirm short-window volume and trade count. |
| Tile size by open interest | Larger tiles have more outstanding perp exposure.                       | Check whether open interest is rising with price or only concentrated in one market.                                 |
| 24-hour color              | Green markets are up over 24 hours; red markets are down over 24 hours. | Use [Compare](/features/compare.md) to see relative performance from a custom start point.                           |
| Outlier tile               | A market differs strongly from the rest of the board.                   | Open it in [Terminal](/features/hyperliquid-trading-terminal.md) and validate chart, orderbook, and news context.    |
| Sector movement            | Several related markets move together.                                  | Check whether the move comes from news, broad risk appetite, or funding pressure.                                    |

## Trading workflow

1. Open [app.proliquid.xyz/heatmap](https://app.proliquid.xyz/heatmap).
2. Select the exchange and grouping method.
3. Look for large tiles with unusual color relative to the rest of the market.
4. Click a market tile to open it in [Terminal](/features/hyperliquid-trading-terminal.md).

Pair Heatmap with [Screener](/features/crypto-screener-for-hyperliquid-traders.md) when you want exact volume, trades, volatility, funding, and open-interest metrics.


---

# 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://docs.proliquid.xyz/features/heatmap.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.
