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

# Orders and History

**Every trade you place, every order you queue, every market move beside them — in one panel.**

The Orders panel sits under the trading chart and consolidates four views: public token flow, your token-specific holdings, your open and recent orders, and your full lifetime activity. Switch tabs to move between the market and your own actions without leaving the trading screen.

{% hint style="success" %}
**Stay on one screen**

Watch the order book, your active limits, and your fill history — without tab-juggling.
{% endhint %}

## Transactions

Public token activity — use this tab to read the tape. Recent buys and sells for the token in focus, with initiator wallets and Solscan links for forensic follow-up.

Columns:

* **Date / Age** — when the trade happened.
* **Type / Initiator** — what it was and who placed it.
* **Price / Amount / Total** — execution data.
* **TXN** — Solscan link.

## My Assets

Holdings for the current token. Use this tab to see what you own, what's still in the bag, and what's already been realized.

Visible fields:

* **Date / Token / Wallet** — provenance.
* **Invested / Remaining / Sold** — position lifecycle.
* **P\&L changes** — running performance.
* **Actions** — quick re-trade or cancel.

Filters include `Hidden` and `Zero balance` for tidying long lists when you hold dust across many tokens.

## My Orders

Your order records — active, finished, or errored. The same tab that limit orders land in after submission.

Status buckets:

* **Active** — open orders awaiting fill.
* **Completed** — filled orders.
* **Error** — orders that hit a failure condition.

Columns: Date, Price, Token, Type, Direction, Status, Instrument, Actions. If no orders match the token in focus, the table reads `No orders found`.

## Transaction History

Your full trade ledger. Use this tab for retrospective review or to audit a failed session.

Status buckets:

* **Completed** — successful trades.
* **Error** — failed transactions.
* **Cancel** — orders you cancelled.

Columns: Date, Token, Wallet, Direction, Amount, Price, Volume, Status, Instrument, Actions.

## When to Use Which Tab

* **Reading the market right now** — Transactions.
* **Checking what you currently hold** — My Assets.
* **Watching open limit orders** — My Orders → Active.
* **Investigating a failed trade** — Transaction History → Error.
* **Auditing a session** — Transaction History (all).

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/9eGnSJYwMzxUn7JuFHHI"><strong>Limit Orders</strong></a></td><td>How orders enter the Active bucket.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr><tr><td><a href="/pages/9RpnN8ylaCXqw4dJTBnq"><strong>Market Orders</strong></a></td><td>Immediate-fill flow and what lands in Completed.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr><tr><td><a href="/pages/5Xes96FGqPBItzknZigD"><strong>Execution Risks</strong></a></td><td>Why orders move to Error and how to read the cause.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
Need to understand why an order shows Error? See [Execution Risks](/graphdex-docs/trading/execution-risks.md).
{% endhint %}

## FAQs

<details>

<summary>Why is my order in Error instead of Completed?</summary>

Order errors come from a wallet, network, or pool-level condition — insufficient gas, slippage tolerance exceeded, liquidity shortfall, or a routing failure. Open the row's Actions to see the cause; \[Execution Risks]\(execution-risks.md) covers the common patterns.

</details>

<details>

<summary>How long does My Orders keep an Active limit visible?</summary>

Until the order fills, errors, or you cancel it. There is no automatic expiry; review the Active list periodically.

</details>

<details>

<summary>What's the difference between My Orders and Transaction History?</summary>

My Orders focuses on the order lifecycle (Active / Completed / Error). Transaction History is the full ledger of trades, including cancelled and failed ones, for retrospective review.

</details>

<details>

<summary>Can I filter by token in Transactions?</summary>

The Transactions tab is scoped to the token currently in focus on the trading screen. Switch tokens via the token search or token page to refresh the feed.

</details>

<details>

<summary>Why does My Assets show fewer entries than I expect?</summary>

Default filters hide zero-balance and hidden tokens. Toggle the \`Hidden\` or \`Zero balance\` filter to surface them.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/trading/orders-and-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.