> For the complete documentation index, see [llms.txt](https://help.keyring.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.keyring.app/keyring-pro/how-to-use/pinned-transaction.md).
# Pinned Transaction
Pinned transactions allow users to pin and store important transactions, making it easier to manage and keep track of them.
## How to pin a transaction
When you complete a transaction, KEYRING PRO Wallet provides you with a transaction hash (TXH for short)
Next to the TXH, you'll see an icon for pinning. Tap that icon to pin the transaction.\
You can view all your pinned transactions in the **Pinned Transaction** tab on the main screen.
## Add a memo
In the **Pinned Transaction** tab, swipe left on a saved transaction. You'll see two options: **Delete** and **Add Memo**.
* **Add Memo:** Use this to add notes or reminders to your pinned transaction for better clarity.
* You can edit a memo the same way. If you want to delete a memo, just leave the content blank while editing.
## Delete Pinned Transactions
To delete a pinned transaction, swipe left on the transaction and select "Delete."
---
# 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://help.keyring.app/keyring-pro/how-to-use/pinned-transaction.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.