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

# Trading Volume and History

<figure><img src="/files/vH6m5wuo8kA3aNJ37kdN" alt=""><figcaption></figcaption></figure>

You can see a real-time transaction flow in our Trading History area.&#x20;

A green arrow up indicates a transaction was a buy; a red arrow down means it was a sell.&#x20;

If we have enough data about the wallet that a trader used, we will add an icon to the transaction indicating the type of trader.&#x20;

#### **Icons**

🐢 - Casual Trader with $10k-$100k of a trading volume in the last 30 days

🦈 - Active Trader with $100k-$500k of a trading volume in the last 30 days

🐳 - Heavy Trader with $500k+ of a trading volume in the last 30 days

🤖 - Trader with 1000+ TXs in the last 30 days. Most likely a bot.<br>

<figure><img src="/files/NHUYV3YLXC7TQ6m4rOyN" alt=""><figcaption></figcaption></figure>


---

# 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.dex.guru/features/trading-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.
