> For the complete documentation index, see [llms.txt](https://doc.suprage.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.suprage.app/user-guide/pages/network-analytics.md).

# Network Analytics

**Route:** `/dapp/network_analytics`

Network Analytics is the **Supra network monitor**: a live look at how the chain itself is performing — throughput, block times, and load — sampled directly from recent blocks.

## What it shows

* **TPS** — current, average, and peak transactions per second.
* **Block time** — average time between blocks.
* **Gas per block** and **transactions per block**.
* **Network load** — a composite gauge of how busy the chain is.
* **History** — TPS and gas plotted over time so you can spot surges.

## How it works

This page reads blocks **directly from the Supra mainnet RPC** in your browser, sampling the latest block and recent history to compute the metrics live. (Reading the chain directly — rather than through the server — keeps this high-frequency polling efficient.) You can **pause/resume** the live sampling with the play/pause control.

## How to read it

* A **rising TPS with stable block time** = healthy, busy network.
* **Block time creeping up** under load can hint at congestion.
* Compare network surges against market events on [Market Radar](/user-guide/pages/market-radar.md) — big market moments often coincide with on-chain activity spikes.

## Tips

* Use **pause** when you want to study a snapshot without the numbers shifting.
* Peak TPS is a good "how hot can it get?" reference for the network during busy periods.


---

# 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://doc.suprage.app/user-guide/pages/network-analytics.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.