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

# Wallet Tracker

**Watch the wallets that matter — every transaction, every token, every move.**

<div align="center"><figure><img src="/files/AnuIRgx3Ju4HdXa1cEG3" alt="Wallet Tracker setup view"><figcaption><p>Setting up wallets, Import / Export / Add wallet controls, and the address search.</p></figcaption></figure></div>

Wallet Tracker is the surveillance side of GraphDex — pick wallets to follow, label them, and watch their activity in real time. Useful for studying smart-money behaviour, monitoring known whales, or auditing your own positions across multiple addresses.

{% hint style="success" %}
**Labels are for you**

A wallet's on-chain address never changes; the label is your private nickname for the tracker.
{% endhint %}

## Add Wallets

Two paths to start tracking:

* **Add Wallet** — manual entry. Enter the wallet address, an optional label, and save. The flow shows a success state when the wallet is added.
* **Import** — bulk import. The flow validates each address and surfaces invalid-address feedback for failed rows.

If an address is rejected, double-check the format and the network — Solana addresses are base58 strings of a specific length.

## Wallet List

Once added, watched wallets show as a list with:

* **Name or label** — your nickname for the wallet.
* **Wallet address** — the on-chain address.
* **Date or update time** — when activity last refreshed.
* **Actions** — row-level controls.
* **Stats** — summary metrics.

Labels exist for **your organization**; they don't change the underlying address or anything visible on-chain.

## Wallet Activity

The activity table is where the tracking pays off — every move from a watched wallet shows up:

* **Type** — buy, sell, transfer, swap, etc.
* **Token** — what moved.
* **Market cap** — context at the time of activity.
* **Amount** — size of the move.
* **Transaction reference** — link to the on-chain record.
* **Date / creation time** — when it happened.

When **transaction references / explorer links** are available, use them to verify activity outside GraphDex. Block explorers are the ground truth; the tracker view is the friendly presentation.

## Settings and Trading Views

Wallet Tracker also exposes:

* **Settings** — manage tracked wallets, edit labels, configure notifications.
* **Trading view** — review wallet actions in a trading-oriented layout.

Use Settings to keep the watchlist tidy. Use the trading view to decide whether a watched wallet's activity is worth researching further.

## 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/2PlFU4Pt3OKOoBaNMfAK"><strong>Twitter/X Tracker</strong></a></td><td>The social side of the same surveillance flow.</td><td><a href="/files/OVXlon60XqRGRA8pZwho">/files/OVXlon60XqRGRA8pZwho</a></td></tr><tr><td><a href="/pages/AVlBX9c7pQQjTospVQGB"><strong>Notifications</strong></a></td><td>How tracker events surface as alerts.</td><td><a href="/files/AnuIRgx3Ju4HdXa1cEG3">/files/AnuIRgx3Ju4HdXa1cEG3</a></td></tr><tr><td><a href="/pages/XJTcByJsbupiZnUUjdb4"><strong>Using Tracker with Research and Trading</strong></a></td><td>How wallet signals flow into the research → trade pipeline.</td><td><a href="/files/JBN29ujDJykAmMONwLxK">/files/JBN29ujDJykAmMONwLxK</a></td></tr></tbody></table>

{% hint style="info" %}
A tracked wallet's signal is a hypothesis — not a buy recommendation. Always cross-reference with [Research](/graphdex-docs/research/research-overview.md) before acting on a watched wallet's trade.
{% endhint %}

## FAQs

<details>

<summary>How many wallets can I track at once?</summary>

The limit depends on your account tier and the current product version. Import flows handle bulk additions; check the panel for any explicit cap.

</details>

<details>

<summary>Can a tracked wallet see that I'm watching them?</summary>

No. Wallet Tracker is local to your view — there's no on-chain action and nothing visible to the watched wallet.

</details>

<details>

<summary>Why do some transactions appear delayed?</summary>

Indexing latency. The tracker pulls from on-chain data, which can lag by a few seconds during high network activity.

</details>

<details>

<summary>Can I export my watchlist?</summary>

Yes — the Import / Export controls expose both directions. Useful for backing up your watchlist or sharing it across accounts.

</details>

<details>

<summary>What happens to alerts if I delete a tracked wallet?</summary>

Notifications tied to that wallet stop. Existing alert history may remain in the notification log depending on the current product version.

</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/tracker/wallet-tracker.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.