> For the complete documentation index, see [llms.txt](https://docs.haust.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.haust.network/haust-wallet/telegram-miniapp/history.md).

# History

1\. Tap \[History] on the Haust Wallet home screen to view all transactions. 

<figure><img src="/files/G0jaapBIIjYPuSxPS1ub" alt="" width="188"><figcaption></figcaption></figure>

Alternatively, select a token from your asset list and tap \[History] to filter by that token.

<figure><img src="/files/O8MfHq3P61LI10zNyqO5" alt="" width="188"><figcaption></figcaption></figure>

2\. If no transactions exist, this will be indicated.

<figure><img src="/files/3LNdo8S1GLpLFh7EGZ4F" alt="" width="188"><figcaption></figcaption></figure>

3\. Pending transactions appear at the top of the screen.

<figure><img src="/files/jN2m1dBtq2ALLXwfrxc8" alt="" width="188"><figcaption></figcaption></figure>

4\. Transactions are grouped by date and sorted from recent to older.

<figure><img src="/files/iB1Z1EhrD1GS9d42sn3t" alt="" width="188"><figcaption></figcaption></figure>

5\. Use the filter icon to adjust the history view by token, transaction type, status or date range.

<figure><img src="/files/AEjdNhwMWaTQbtaOuM7v" alt="" width="188"><figcaption></figcaption></figure>


---

# 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.haust.network/haust-wallet/telegram-miniapp/history.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.