> 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/tutorials/4.-dashboard-portfolio-and-activity.md).

# 4. Dashboard, Portfolio and Activity

Read your performance at a glance and trace any trade, down to the batcher fee.

{% embed url="<https://drive.google.com/file/d/1O_KY5p-o_VQSD3Ur1ujAN9oQKoK2ZkNm/preview>" %}

Surge accounts for every ADA in and out. The Dashboard shows how your strategies are doing right now. Portfolio adds up your totals, and Activity keeps the full audit trail.

### What you'll learn

* Reading portfolio value and P\&L
* Managing strategies from the Active Strategies table
* Understanding fees and returns in Portfolio
* Tracing any trade in Activity

### Dashboard

| Section             | What it shows                                                                          |
| ------------------- | -------------------------------------------------------------------------------------- |
| Portfolio Value     | Total value across your wallets, with today's P\&L                                     |
| Realized P\&L (30D) | Profit or loss from closed round trips over 30 days, and how many trades were measured |
| Active Strategies   | Every strategy with estimated P\&L, 24h volume, trades and last activity               |
| Recent Activity     | The latest trades with DEX, pair, side, input, output, fees and status                 |

In **Active Strategies** you can filter by running or paused, search, sort, or export to CSV. The eye icon opens a strategy, and the pause icon pauses it right from the table.

### Portfolio

* **Trading activity:** order count, buy and sell split, volume and average size
* **Fees paid:** split into Surge, batcher, network and pool fees
* **Returns:** all-time and 7-day performance
* **Realized P\&L by strategy:** P\&L, win rate and closed trades per strategy

### Activity

Activity is your full audit trail: every trade, signature and on-chain action.

* Switch between the **Transactions** list and the **Calendar** view
* Filter by buys or sells
* Expand any row for the full fee breakdown
* Follow the transaction hash to Cardanoscan
* Export everything to CSV for your records

### Good to know

* **Realized vs estimated.** Realized P\&L counts closed round trips only. Estimated P\&L also marks open positions at the current price.
* **Tax time.** The Activity CSV export gives you every trade, fee and transaction hash.

### Next

[5. Swap across Cardano DEXes](/tutorials/5.-swap-across-cardano-dexes.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 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/tutorials/4.-dashboard-portfolio-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.
