> For the complete documentation index, see [llms.txt](https://docs.octusbridge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octusbridge.io/ob-jp/bridge/history/interface/all-transfers.md).

# 全ての転送

[**履歴項目**](https://app.octusbridge.io/transfers)の最後は［**全ての転送**］です。

Octus Bridgeを使用して最近行われたトランザクションが全てここに表示されます。\
どのトランザクションにも、そのトランザクションに関する下記の情報を示す項目があります：

* 転送量(トークン)
* トランザクションタイプ
* 差出人と受取人のネットワークとアドレス
* 転送日

ブロックの右上では、差出人アドレス、日付、転送元および転送先ブロックチェーン、転送トークン、トランザクションステータスおよびタイプを選択できるトランザクション**検索フィルター**を有効にして設定することができます。

![](/files/D1RgacCH91h70fLDQO7K)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.octusbridge.io/ob-jp/bridge/history/interface/all-transfers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.