> For the complete documentation index, see [llms.txt](https://userguide.cryptoquant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.cryptoquant.com/zh/flow-indicators/jiao-yi-suo-ju-jing-bi-lv.md).

# 交易所巨鲸比率

前10大交易的比特币总量（就所发送的比特币总量而言）与流入交易所的比特币总量的比值。

## Definition

The total BTC amount of the top 10 transactions (in terms of total BTC sent) divided by the total BTC amount flowing into exchanges.<br>

$$
\text{Exchange Whale Ratio} = \frac{\text{Sum of Top 10 Exchange Inflow TXs(BTC)}}{\text{Total Exchange Inflows in BTC}}
$$

## Interpretation

Find Whale Focused Exchanges with Top 10 Inflows. Looking at the relative size of the top 10 inflows to total inflows, it is possible to discover which exchanges whales use. For example, as Gemini has mostly whale users, it is possible for the price to rise or fall dramatically. This has potential risks, but also the possibility of arbitrage.

## Link to Our Data

* [Exchange Whale Ratio in CryptoQuant Live Chart](https://cryptoquant.com/overview/full/595?window=day)
* [Exchange Whale Ratio in CryptoQuant Data API docs](https://cryptoquant.com/docs#operation/getExchangeWhaleRatio)


---

# 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://userguide.cryptoquant.com/zh/flow-indicators/jiao-yi-suo-ju-jing-bi-lv.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.