> 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/es/market-data-indicators/exchange-whale-ratio.md).
# Proporción de Ballenas en Exchange
La cantidad total de BTC de las 10 principales transacciones (en términos del total de BTC enviados) dividida por la cantidad total de BTC que entra en el exchange.
## Definición
La cantidad total de BTC de las 10 principales transacciones (en términos de BTC total enviado) dividido por la cantidad total de BTC que fluye en los exchanges.
$$
\text{Proporción de Ballenas en Exchange} = \frac{\text{Sum de Top 10 Transacciones Entrantes del Exchange (BTC)}}{\text{Total Entradas Exchange en BTC}} \
$$
## Interpretación
Encuentre los exchanges centrados en la ballena con los 10 principales flujos de entrada. Observando el tamaño relativo de los 10 principales flujos de entrada con respecto al total, es posible descubrir qué exchanges utilizan las ballenas. Por ejemplo, como Gemini tiene mayoritariamente usuarios balleneros, es posible que el precio suba o baje drásticamente. Esto tiene riesgos potenciales, pero también la posibilidad de arbitraje.
## Enlace a nuestra Data
* [Gráfico de Proporción de Ballena en Exchange en CryptoQuant](https://cryptoquant.com/overview/full/595?window=day)
* [Documentos de Datos API de Proporción de Ballena en Exchange en CryptoQuant](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/es/market-data-indicators/exchange-whale-ratio.md?ask=&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.