> 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/whale-alerts-and-large-trades.md).

# Whales

Follow whale alerts, large Hyperliquid trades, and major liquidation events to understand where size is entering or exiting.

<figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2F52XwbRoP2pQ3jhr4EAG6%2Fimage.png?alt=media&amp;token=5dcb0c97-cea6-4014-b7ab-c943846b4159" alt="Whales feed showing large Hyperliquid trades and liquidation activity."><figcaption><p>Whales feed showing large Hyperliquid trades and liquidation activity.</p></figcaption></figure>

Use Proliquid Whales to track large Hyperliquid trades, whale alerts, and liquidation activity so you can see where size is entering or being forced out.

Use it to find addresses worth watching, identify aggressive buying or selling, and notice when large traders are being liquidated. Whale and liquidation notification behavior is summarized in [Alerts](/features/alerts.md).

## What the data means

| Signal            | What it means                                               | What to check next                                                                                                             |
| ----------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Large trade       | A high-notional trade printed on Hyperliquid.               | Check whether it moved price or was absorbed by liquidity.                                                                     |
| Repeated address  | The same public address appears multiple times.             | Use [Spectate mode](/terminal-sections/spectate-mode.md) to inspect public context.                                            |
| Whale liquidation | A large position was forced out by exchange risk mechanics. | Check [Liquidation](/features/crypto-liquidations-tracker.md) and the [Chart](/terminal-sections/chart.md) for follow-through. |
| Directional flow  | Multiple large trades appear in the same direction.         | Confirm with [Screener](/features/crypto-screener-for-hyperliquid-traders.md) volume delta and orderbook depth.                |
| Isolated event    | One large print appears without broader confirmation.       | Treat it as context until price, volume, or news confirms it.                                                                  |

## What to look for

* Repeated large trades from the same address.
* Large liquidations during a fast move.
* Whale trades that align with news, funding, or screener alerts.
* Markets where one side is being forced out.

Click a market symbol to open it in [Terminal](/features/hyperliquid-trading-terminal.md) with chart, orderbook, and position context.

Open [Whales in Proliquid](https://app.proliquid.xyz/whales). Related: [Alerts](/features/alerts.md) and [Liquidation](/features/crypto-liquidations-tracker.md).

> Large trades are useful context, but they do not explain the trader's full portfolio or intent. Use them with price, liquidity, and market context.


---

# 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/whale-alerts-and-large-trades.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.
