> For the complete documentation index, see [llms.txt](https://docs.liquidus.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquidus.finance/liquidus-wallet-app/wallet-basics/check-your-transaction-history.md).

# Check your transaction history

1. Make sure you are on the “Wallet” page. From there click the “History” button located underneath your main portfolio value.
2. If you have pending transactions, they will show up under the “Pending” section. Confirmed transactions appear under the “History” section. For most networks, transactions are confirmed within a few seconds. 
3. It shows you the date and time of the transaction, as well as what has been done. For example “Send USDC” or “Top Up LIQ-BNB”, etc. 
4. Click on a transaction to view the details, such as transaction hash or farm contracts that have been used. 
5. Please note, that some events such as topping up a farm can have multiple transactions on the blockchain. All steps involved are displayed in one clear overview.


---

# 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.liquidus.finance/liquidus-wallet-app/wallet-basics/check-your-transaction-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.