> 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/ja/inter-entity-flow/exchange-to-exchange.md).

# 取引所から取引所へ

取引所から他の取引所のウォレットに送金されたコインの総量です

## 定義

取引所から他の取引所のウォレットに送金されたコインの合計額

| メトリクス        | 説明                             |
| ------------ | ------------------------------ |
| フロー合計        | 取引所から他の取引所のウォレットに送金されたBTCの合計金額 |
| フロー平均        | 取引所から他の取引所のウォレットに送金されたBTCの平均額  |
| フロートランザクション数 | 取引所から他の取引所のウォレットへの取引数です。       |

平均値は「合計フロー」を「フロートランザクション数」で割ったものです。データエントリは、2つのエンティティ間の最初のトランザクションから収集されました。

## データへのリンク

* [CryptoQuantライブチャートでの取引所間トランザクション ](https://cryptoquant.com/overview?search=Exchange+to+Exchange)
* [CryptoQuant データAPIドキュメントでの取引所間トランザクション](https://cryptoquant.com/docs#operation/BTCgetExchangeToExchange)


---

# 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/ja/inter-entity-flow/exchange-to-exchange.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.