> 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/research/trends.md).
# Trends
**Trends is the sustained-activity view — pick a time window from 1m to 24h and the table sorts the pairs that have been moving over it.**
Trends sits between New (as-it-happens) and Gems (high-signal) in Research. Use it when you don't want the firehose of new appearances and don't yet want the curated end of the spectrum — you want to see which pairs have been doing something over a specific time horizon.
The column set is the same as the rest of Research, with one extra: a **1H** movement column. The time-window selector switches the *context* for the trend view — sorting and selection follow whatever window you pick.
{% hint style="success" %}
**Pick the window that matches your horizon**
Short windows for momentum, long windows for confirmation — the rest of the columns are the same.
{% endhint %}
## TIME WINDOWS
The current Trends tab supports six windows. Wider windows confirm a move, narrower ones surface it.
* **1m**
* **5m**
* **30m**
* **1h**
* **6h**
* **24h**
If there's no matching activity for the current filter and window, the table shows `No records found` instead of a sparse row set.
## WHAT THE TABLE SHOWS
* **Pair** — token symbol and paired asset.
* **Market Cap** — current MC at the time of view.
* **Live Liquidity** — pool depth right now.
* **TXNS** — total transaction count with buy / sell split.
* **Volume** — trade volume for the row over the active window.
* **1H** — price movement over the last hour.
* **Audit** — contract-level risk markers.
## HOW TO READ TRENDS
Use the window selector to match the horizon you're actually trading.
* Short windows (1m / 5m) for scalp-scale momentum and breakout reads.
* Mid windows (30m / 1h) for confirmation that a move isn't a single-block spike.
* Long windows (6h / 24h) for broader activity context.
* Read **Liquidity** and **Volume** together — high volume on thin liquidity is volatility, not trend.
* Watch TXNS with the buy / sell split — a trending row should show two-sided activity.
* Confirm **Audit** before opening the row in Trading.
## FILTERING TRENDS
The Trends filter panel goes further than New's — it adds holder and migration-related controls on top of DEX, audit, and metric filters.
* DEX selectors narrow the source pool.
* Audit filters drop rows that fail your floor.
* Metric filters: liquidity, market cap, volume, TXNS bands.
* Holder filters: **Migration Progress, Dev Holding, Snipers Holding, Insider Holding, Bundler Holding, Top 10 Holders, Number of Holders.**
* Compose them — a tight liquidity floor + clean audit + reasonable Top 10 Holders cap turns a noisy table into a working shortlist.
{% hint style="info" %}
Trends surfaces market activity, not trade signals. Open the [Token Page](/graphdex-docs/trading/token-page.md) before placing an order, and confirm [Trading Settings](/graphdex-docs/trading/trading-settings-overview.md) match the execution profile you want.
{% endhint %}
## FAQs
What time windows does Trends support?
**1m, 5m, 30m, 1h, 6h, 24h.** Pick the window that matches your trading horizon.
Why does the table say No records found?
The current filter set has no matches inside the selected window. Try widening the window, relaxing one filter, or clearing filters entirely to confirm rows do exist outside your current lens.
How is Trends different from New and Gems?
* **New** — as-it-happens feed, no time window.
* **Trends** — sustained activity in a window you pick.
* **Gems** — high-signal candidates by GraphDex terminal metrics, tight windows only.
See [Research Overview](/graphdex-docs/research/research-overview.md) for the full split.
What's the difference between TXNS and Volume?
**TXNS** is the count of trades (with buy/sell split). **Volume** is the value those trades moved. Both can be high; both can be misleading on their own. Read them together with Liquidity.
---
# 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/research/trends.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.