> 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/tr/cryptoquant-metrics/market/exchange-whale-ratio.md).

# Borsa Balina Oranı

En büyük 10 işlemin toplam BTC miktarının (gönderilen toplam BTC bakımından) borsalara akan toplam BTC miktarına bölünerek hesaplanır.

## Tanımı

En büyük 10 işlemin toplam BTC miktarının (gönderilen toplam BTC bakımından) borsalara akan toplam BTC miktarına bölünerek hesaplanır.

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

## Yorumlaman

En Büyük 10 Giriş İşlemi ile Balina Odaklı Borsaları Bulun. En yüksek 10 giriş işleminin toplam girişlere göre oranına bakarak, balinaların hangi borsaları kullandığını keşfetmek mümkündür. Örneğin, Gemini'nin çoğunlukla balina kullanıcıları olduğu için, fiyatın dramatik olarak yükselmesi veya düşmesi mümkündür. Bu potansiyel riskler taşısa da, aynı zamanda arbitraj fırsatı da sunabilir.

## Verilerimize Bağlantı

* [Borsa Balina Oranı Canlı Grafik](https://cryptoquant.com/overview/full/595?window=day)
* [Borsa Balina Oranı CryptoQuant API Dokümanları](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/tr/cryptoquant-metrics/market/exchange-whale-ratio.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.
