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

# Transaction history

HiperSnipe can show recent on-chain swap signatures with a performance summary header.

## Access today

The transaction history handlers exist (`transaction_menu`, `view_last_transaction`, `view_last_10_transaction` in `main.py`), but there is **no main-menu button** wired to `transaction_menu` in `menus.py`.

Operators can still reach history if a keyboard links to `transaction_menu`, or by adding a menu entry in a future release.

## Screens (when opened)

| Action               | Content                                        |
| -------------------- | ---------------------------------------------- |
| Last transaction     | Most recent swap signature, side, amounts      |
| Last 10 transactions | Scrollable list with refresh                   |
| Performance header   | Win rate and summary stats on the last-10 view |

## Trade Journal vs transaction history

| Feature   | Trade Journal            | Transaction history |
| --------- | ------------------------ | ------------------- |
| Main menu | ✅ Yes                    | ❌ Not linked today  |
| Focus     | Closed PnL cycles        | Raw tx signatures   |
| Detail    | Per-close ROI, hold time | On-chain leg data   |

For PnL-focused review, use **Trade Journal**. For signature audit trails, transaction history is the right layer once exposed in UI.

## Related

* [Trade Journal](/features/trade-journal.md)
* [Buy and sell execution](/features/buy-sell.md)


---

# 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.hipersnipe.com/features/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.