> 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/chart-and-token-metrics.md).

# Chart and Token Metrics

**The chart, the header metrics, and the activity tables share one job — give you enough context to size and time an order without leaving the token page.**

<figure><img src="/files/vwRASWagNMucMVv2DBXL" alt="Trading screen — chart and metrics"><figcaption><p>Token page — chart paired with header metrics and activity tables.</p></figcaption></figure>

The chart is the visual layer; the metrics are the numerical layer; the tables are the per-event layer. Each one is useful on its own, but most decisions get made when you read them together — a clean chart on thin liquidity is volatility, a noisy chart with strong volume is signal, and a flat chart with insider concentration is a warning regardless of how the line looks.

{% hint style="success" %}
**Three layers, one read**

Glance at LIQ / MC / 5M Vol → check the movement windows → drop into Transactions and Top holders before sending an order.
{% endhint %}

## CORE METRICS

The header carries the three numbers you read first. They're cheap to glance at and expensive to ignore.

* **LIQ** — liquidity GraphDex shows for the pair right now.
* **MC** — market cap surfaced by the terminal.
* **5M Vol** — short-window volume where available.
* Read them **together** — high MC with thin LIQ is volatility; visible activity with weak Vol is noise.

## MOVEMENT WINDOWS

Four windows on the pair summary, each useful for a different horizon.

* **5M** — very recent movement, scalp-scale.
* **1H** — short-window confirmation.
* **6H** — broader context for the session.
* **24H** — full day-over-day movement.
* Strong movement on a single window doesn't guarantee continued direction — pair with LIQ, Vol, and the chart.

## TRANSACTION TABLE

The **Transactions** tab carries per-trade granularity. Use it to read what's *actually* happening on the pair, not just the aggregate read.

* **Date** — trade timestamp.
* **Age** — relative age (`12s`, `2m`, etc.).
* **Type** — buy or sell.
* **Price** — execution price.
* **Amount** — token amount.
* **Total** — total in the paired asset.
* **Initiator** — wallet that placed the trade (links to explorer).
* **TXN** — transaction hash (links to explorer).
* Use Initiator + TXN links when a trade is suspiciously large to verify on-chain.

## HOLDER AND RISK TABLES

The **Top holders** tab and the token details area together show *who holds supply* — the input that audit and distribution signals operate on.

* **Top holders** — Address, percent of supply, amount, paired-asset value.
* Token details surface concentration markers: **Dev Holders, Top 10 Holders, Sniped, Insiders, Bundled.**
* High concentration in any one bucket is a prompt for closer review on the [Token Page](/graphdex-docs/trading/token-page.md).
* See [Audit Signals](/graphdex-docs/research/audit-signals.md) for the broader vocabulary.

## HOW TO COMBINE THE LAYERS

A 30-second read order that catches most edge cases:

1. **LIQ / MC / 5M Vol** at a glance.
2. **Movement windows** for the horizon you're trading.
3. **Chart** for visual confirmation of the read above.
4. **Transactions tab** for per-event flow (one-sided runs, single-whale moves).
5. **Top holders + token details** for the supply-side risk read.
6. Only then open the order panel.

{% hint style="info" %}
Strong movement isn't a guarantee of continued direction, and a clean chart isn't a guarantee of clean supply. Cross-read across all three layers before sending an order.
{% endhint %}

## FAQs

<details>

<summary>What's the difference between <code>LIQ</code> and <code>MC</code>?</summary>

**LIQ** is current pool depth — what's actually available to trade against. **MC** is the terminal-shown market cap. A token can carry a large MC with thin LIQ, which is one of the most common volatility traps.

</details>

<details>

<summary>Why does <code>5M Vol</code> matter more than 24H sometimes?</summary>

Short windows show **what's happening right now**. A token that traded 1M in volume yesterday but nothing in the last 5 minutes is functionally illiquid for your next order. Use 5M Vol for sizing, 24H for context.

</details>

<details>

<summary>Where do Initiator and TXN links go?</summary>

To a Solana explorer (typically Solscan). Use them to verify a transaction on-chain when an aggregate read looks off.

</details>

<details>

<summary>What's the right read order for a fresh token page?</summary>

Header metrics → movement windows → chart → Transactions → Top holders + token details → order panel. The whole thing is \~30 seconds once you know the pattern.

</details>

<details>

<summary>Can the chart by itself tell me whether to trade?</summary>

No. A clean chart on thin LIQ is volatility, not strength. Always cross-read the chart against LIQ / Vol / transactions / holders before sending an order.

</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/chart-and-token-metrics.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.
