> 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/token-page.md).
# Token Page
**The token page is the trading view for one pair — header metrics, chart, activity tabs, and the order panel all share the same screen.**
Token page — header and chart area.
Open the token page from any Research row, any Pulse card, any Tracker hit, or directly via the Trading navigation. The URL is `/sol/terminal/{token-address}`, so every shared link drops you straight onto the right token. From the moment the page opens, you can read the metrics, scan recent transactions, and prepare an order without leaving the screen.
The page is structured in three vertical layers: a **header** with token identity and macro metrics, a **middle** with chart, pair summary, and activity tabs, and a **right rail** with the order panel and position summary. Token details and risk indicators sit underneath.
{% hint style="success" %}
**One token, one screen**
Header metrics, chart, activity, order panel — everything you need for a trade in one view.
{% endhint %}
## HEADER INFORMATION
The header is the at-a-glance read: who the token is and what its macro state looks like right now.
* **Token name** and **symbol**.
* **Token / Pair** controls — switch the side of the pair shown.
* **LIQ** — liquidity value displayed by the terminal.
* **MC** — market cap.
* **5M Vol** — short-window volume where available.
* Pair the header read with the chart before opening the order panel.
## PAIR SUMMARY
Right under the header, the pair summary shows the selected pair (e.g. `C0IN / SOL`) and the venue or source surfaced by the terminal — `Meteora DAMM v2`, `Pump Fun`, etc. Movement windows complete the picture.
* **5M / 1H / 6H / 24H** — price-direction movement windows.
* Movement windows show **direction**, not depth — pair them with **LIQ** and **5M Vol** for sizing.
* The venue tag is useful when filtering: a token on a venue you trust differs from a token on a venue you don't.
* See [Chart and Token Metrics](/graphdex-docs/trading/chart-and-token-metrics.md) for the chart's deeper read.
## ACTIVITY SUMMARY
The activity summary collapses recent flow into three numbers.
* **Buys** — count and value of recent buys.
* **Sells** — count and value of recent sells.
* **Net Vol** — the *net* of buys and sells over the same window. Not total volume.
* Read Net Vol with the buy / sell split — a positive Net Vol on a thin liquidity row is still volatile.
## TOKEN ACTIVITY TABS
Under the chart, the tabs split public activity from your account-level data — public on the left, personal on the right.
* **Transactions** — recent on-chain trades for the pair.
* **Top holders** — concentration of supply at the time of viewing.
* **My assets** — your wallet holdings of this token.
* **My orders** — your active orders on this pair.
* **Transaction history** — your prior trades on this pair.
* Use the public tabs for context, the personal tabs for sizing the next move.
## TOKEN DETAILS — SECURITY AND DISTRIBUTION
Token details live below the chart. Read them as **prompts for review**, not as guarantees.
* **Security** — contract-level audit markers.
* **Dev Holders** — share held by the dev wallet.
* **Top 10 Holders** — concentration in the top 10 wallets.
* **Sniped** — supply attributed to sniper wallets at launch.
* **Insiders** — share held by flagged insider wallets.
* **Bundled** — supply acquired via bundlers at launch.
A clean-looking row of details still doesn't override a hard look at the chart, liquidity, and recent transactions.
{% hint style="warning" %}
Token details surface risk signals; they don't guarantee safety. Never approve a wallet prompt you don't understand. See [Audit Signals](/graphdex-docs/research/audit-signals.md) for how to read the indicators.
{% endhint %}
## FAQs
How do I open the token page for a token?
Click any row in [Research](/graphdex-docs/research/research-overview.md), any card in [Pulse](/graphdex-docs/pulse/pulse-overview.md), or any [Tracker](/graphdex-docs/tracker/tracker-overview.md) hit. You can also paste a `/sol/terminal/{token-address}` URL.
What does Net Vol mean?
The net of buys and sells over the same window — buys minus sells. It is **not** a total volume figure. Read it alongside the buy / sell split for direction.
What's the difference between LIQ, MC, and 5M Vol?
* **LIQ** — pool depth right now.
* **MC** — market cap.
* **5M Vol** — traded value in the last 5 minutes (where available).
A token can show high MC, low LIQ, and minimal 5M Vol — those three numbers together tell a different story than any one of them in isolation.
How do I read the security/distribution signals?
As triggers for a closer look. **Dev Holders**, **Top 10 Holders**, **Sniped**, **Insiders**, **Bundled** all point at *who controls supply*. None of them by themselves approve a trade — they prompt review on the [Token Page](/graphdex-docs/trading/token-page.md) and in [Audit Signals](/graphdex-docs/research/audit-signals.md).
Where do I see my own orders for this token?
On the **My orders** tab. **Transaction history** carries your past trades on the same pair. For a cross-token view, see [Orders and History](/graphdex-docs/trading/orders-and-history.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 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/token-page.md?ask=&goal=
```
`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.