> For the complete documentation index, see [llms.txt](https://docs.unstable.run/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unstable.run/for-users/trades-and-holders.md).

# Trades & holders panel

Two live surfaces flank the chart on every token page.

## Recent trades

Below the chart, a compact table lists the **last 30 swaps** on the token's pool. Refreshes every 5 seconds, so a trade that just landed on-chain shows up within \~5-10 seconds.

| Column | What it shows                                                                    |
| ------ | -------------------------------------------------------------------------------- |
| Time   | Relative age of the swap ("12s ago", "3m ago", "1h ago").                        |
| Side   | `BUY` in green (USDT0 flowed into the pool) or `SELL` in red (USDT0 flowed out). |
| Amount | Number of tokens moved.                                                          |
| USDT   | USDT0 value of the swap.                                                         |
| Price  | The pool price after the swap.                                                   |
| Wallet | Short address of the trader — clickable, opens the transaction on StableScan.    |

### How "realtime" it really is

Under the hood: the browser polls `/api/trades/[token]` every 5 seconds. That endpoint is edge-cached for 5 seconds, so within the same second every visitor gets an identical answer straight off the Vercel CDN. When a trade actually lands on-chain, the next poll picks it up. Expected delay: **5-10 seconds**.

If you want a truly zero-latency feed (WebSocket subscription to the pool's `Swap` event), that's on the roadmap.

## Holders count

The side stats block in the trade panel shows **Holders** — the number of distinct wallets currently holding a non-zero balance of the token. Refreshes once per minute.

### How it's computed

1. Scan the token's `Transfer` events from the last \~1-3 hours.
2. Collect every recipient address.
3. Batch-call `balanceOf` to filter out addresses whose current balance is zero.
4. Return the surviving count.

For tokens launched within the last few hours this catches everyone. For older tokens with heavy churn, the count may slightly undercount holders whose entire on/off flow happened before the lookback window.

## Side stats block

Under the trade buttons, four rows summarise the token at a glance:

| Row                    | Meaning                                                                                     |
| ---------------------- | ------------------------------------------------------------------------------------------- |
| **Market cap**         | `current price × 1B total supply`. Every token has fixed 1B supply, so mcap = 1B × price.   |
| **24h volume**         | Sum of USDT0 volume across all `Swap` events in the last 24h. `$0` until first trades land. |
| **Holders**            | Non-zero wallet count. See above.                                                           |
| **Liquidity (approx)** | Rough estimate — approximately 42% of market cap for a fresh single-sided pool.             |

{% hint style="info" %}
Because Unstable pools start **single-sided** (100% of supply on the token side, 0 USDT0 on the quote side), the classic "TVL" metric doesn't fit naturally. The Liquidity row is an approximation that gets more accurate as trades push liquidity into balance.
{% endhint %}

## What you can build on top

Everything on this page is derivable from three public event streams:

* `Swap` on the pool → candles, trades, volume
* `Transfer` on the token → holders, transfer graph
* `TokenLaunched` on the factory → registry, per-launch metadata

See [Events & indexing](/on-chain-reference/events.md) for the full event schemas.


---

# 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://docs.unstable.run/for-users/trades-and-holders.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.