> For the complete documentation index, see [llms.txt](https://docs.zenprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenprotocol.com/apps/wallet/wallet-structure/my-wallet/transaction-history.md).
# Transaction History
In the table you will be able to check on which block a transaction was made, the asset & amount was sent/received and the number of confirmations of each transaction.
### **Transaction Status**
The status ‘Pending’ indicates that a transaction has yet to be added to a block even if it was propagated in the network and has a zero confirmation.
**Transaction Information**
To get more information about a transaction, click the ‘Tx Hash’. This will redirect you to the transaction page in the Block Explorer.
To get more information about an asset, like the total issued, it’s distribution etc, click the ‘Asset’. This will redirect you to the asset page in the Block Explorer.\
---
# 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.zenprotocol.com/apps/wallet/wallet-structure/my-wallet/transaction-history.md?ask=&goal=
```
`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.