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

# Activity and trade history

[4. Dashboard, Portfolio and Activity](/tutorials/4.-dashboard-portfolio-and-activity.md) to filter activity and inspect a trade.

The **Activity** page (sidebar → Activity) lists every transaction Surge has submitted for you — swaps, strategy orders, funding transfers, sends and cancels — newest first, 20 per page, refreshed every 15 seconds. Each row expands to show fees, amounts and links to the transaction on Cardanoscan.

### What a row shows

| Column    | Meaning                                                                                                                      |
| --------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Side      | Buy, Sell, or Transfer (funding, send, cancel)                                                                               |
| Status    | Submitted / Open / Filled / Cancelled / Dropped / Unknown — see [Order statuses](/orders-and-transactions/order-statuses.md) |
| Type      | Manual swap, Grid, DCA, Arbitrage, Rule-based, Cadence, Send funds, Order cancel                                             |
| Strategy  | The strategy's name, if any                                                                                                  |
| DEX       | Venue                                                                                                                        |
| Pair      | Token / ADA                                                                                                                  |
| Input     | What you put in                                                                                                              |
| Output    | What you received (Filled rows) or expected (Open rows)                                                                      |
| ADA value | The ADA side of the order                                                                                                    |
| Fee       | Batcher + Surge + pool + network, in ADA                                                                                     |
| Time      | Submission time                                                                                                              |

Expanding a row shows the fee breakdown card, amount placed and received, the effective price and how it compares with the quote ("vs. quote %"), the executing wallet, and the order, fill and refund transaction links. Token amounts are formatted with the token's registered decimals; if a token's decimals are unknown the amount is left blank rather than shown in raw units.

### Filters and the 24-hour summary

Filters: side, status, type, DEX, pair, token, amount range, date range. An active-filter badge and **Reset all** sit above the table.

Filtering runs on **the page you are looking at**, not on your whole history. The 24-hour summary tiles (trades, volume, fees, average fee per trade) likewise summarise the rows on the current page that fall in the last 24 hours, and exclude transfers. For a full-account picture use the Dashboard and Portfolio pages.

### Calendar view

The calendar toggle shows a monthly heat-map of realized P\&L per day (from the same data as the Portfolio page). Future months are blocked.

### Export

**Export CSV** downloads the rows on the current page. Cells beginning with `=`, `+`, `-` or `@` are prefixed with an apostrophe so a spreadsheet does not execute them.

### Other places history appears

* **Dashboard → Recent activity**: the latest 20 orders with stuck-order recovery.
* **Strategy detail → Trade log**: that strategy's orders, plus strategy-specific views (grid cycles and rungs, rule executions, arbitrage opportunities and the decision Activity feed, cadence schedule).
* **Wallet detail**: on-chain transaction history for one wallet (from the chain, so it includes transactions Surge did not make), paginated.
* **Cardanoscan links** on every hash for the on-chain view.

### What history does not include

Orders you placed outside Surge with the same wallet appear only in the wallet detail page's on-chain history, not in Activity. Surge's own records begin at the moment a transaction is submitted through Surge; a transaction that was submitted but whose record failed to save is alerted to Surge's team and may be missing from your list until fixed.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.surgecardano.com/orders-and-transactions/trade-history-and-activity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.