> 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/wallet-predictions/transactions.md).

# Transactions

**Every deposit, withdrawal, swap, and liquidity move tied to the selected wallet — in one filterable feed.**

{% hint style="info" %}
Same wallet as Solana. The chain selector at the top right of the header switches the viewing context; balances, history, and actions on this page apply to your account regardless of side.
{% endhint %}

The Transactions view is the chronological side of the Wallet panel. Where [Assets and Balances](/graphdex-docs/wallet-predictions/assets-and-balances.md) shows *what you hold*, Transactions shows *how it got there* — trades, transfers, deposits, withdrawals, liquidity activity — for the selected wallet and network.

{% hint style="success" %}
**One feed, four filters**

Status filters let you separate completed activity from pending, hidden, errored, or freshly-created records.
{% endhint %}

## Transaction Types

The history view classifies activity by kind:

* **Deposit** — funds arrived at this wallet.
* **Withdraw** — funds left the wallet.
* **Add / Remove / Rebalance Liquidity** — LP-side operations.
* **Swap In / Swap Out** — token-for-token exchanges.

For trading-related rows, you may also see direction tags — **Buy**, **Sell**, **Transfer**, **Withdraw** — surfacing the user-side intent.

## Transaction Statuses

Filter chips at the top of the table:

* **Completed** — successful transactions.
* **Error** — failed transactions.
* **Active** — in-flight.
* **Created** — newly initiated, not yet broadcast.
* **Hidden** — rows you've manually hidden.

Combine filters when you need a specific slice — e.g. `Error` + `Active` to audit failures from the last hour.

## Reading a Row

Each row compresses a transaction into the most relevant fields:

* **Date and time** — when it happened.
* **Wallet / transfer path** — source and destination.
* **Token or instrument** — what moved.
* **Price / Volume / Amount** — the size of the move.
* **Direction** — Buy, Sell, Transfer, etc.
* **Status** — Completed, Error, Active, Created.
* **Actions** — open in explorer, hide, re-trade.

When an **explorer action** is available, use it to open the transaction on Solscan (or the equivalent block explorer) and verify the on-chain record. That's the ground truth — the terminal view is a presentation layer.

## Export

When the `Export` control is visible, you can download wallet history for your own records.

Exports are **informational, not authoritative**. Always verify important balances and transfers against the wallet itself and the relevant block explorer before relying on the data for accounting or operational decisions.

## 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/lCOHuDatyfvwDoIIEXk7"><strong>Assets and Balances</strong></a></td><td>The portfolio view of the same data.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/sHGQJ3BmrBOccgISxByE"><strong>Wallet Security Notes</strong></a></td><td>How to verify a transaction before approving it.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/VpmkMK2En9UqElxOb2n7"><strong>Orders and History</strong></a></td><td>The trading-side ledger of the same transactions.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
A row marked `Error` in Transactions usually surfaces the cause in the explorer. Cross-check before re-submitting the same operation.
{% endhint %}

## FAQs

<details>

<summary>Why is a recent transaction missing from the feed?</summary>

The feed updates in near real-time, but indexing can lag a few seconds on busy blocks. Check the block explorer directly if a transaction doesn't appear after 30–60 seconds.

</details>

<details>

<summary>What does "Hidden" mean here?</summary>

Hidden affects display only — the transaction still exists on-chain and in the wallet's full history. Re-enable hidden rows from the filter chips when you want them back.

</details>

<details>

<summary>Can I edit or delete a transaction record?</summary>

No. Transactions are on-chain records; only the \*\*display\*\* is configurable. Hide / show controls the panel view.

</details>

<details>

<summary>What's the fastest way to audit a failed swap?</summary>

Open the row's Actions menu → block-explorer link. The explorer shows the exact failure reason at the protocol level.

</details>

<details>

<summary>Is Export available on all networks?</summary>

Availability depends on the current product version and the selected network. If the Export control isn't visible, the view is in-app only for that network at the moment.

</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/wallet-predictions/transactions.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.