> For the complete documentation index, see [llms.txt](https://docs.aptscan.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aptscan.ai/browsing-the-site/analytics/aptos-network.md).

# Aptos Network

The dashboard provides in-depth analytics and sub-minute updates on the stats of the Aptos blockchain. Let's dive in to see the details!

**I. Network**

Aptoscan Dashboard gives end user an overview of the current network state, with the following info that can be found useful

<figure><img src="/files/PYfdrQhS1nPAtfvTBnqb" alt=""><figcaption></figcaption></figure>

* Total transaction: number of transactions already taken place on the network
* TPS - All transactions:&#x20;
* Peak user TPS: the highest number of TPS within the last 30 days
* Total fees: total amount of fees generated for the Aptos Network
* Active Validators; Number of active validators on the network
* Total staking: total amount of APT staked to secure the network

The second section of the pic above showcases the number of TPS (blue bar)  and transaction sucesss rate within the 30-day period. You can hover over the chart to reveal exact data on a daily basis.&#x20;

<figure><img src="/files/2ibqP643sUSDNdGEjKSY" alt=""><figcaption></figcaption></figure>

The chart on the left gives and overview of **hourly produced blocks** within the network for the last 30 days.

The chart on the right side is the visualization of **fees generated** by the network, including *daily fees (blue*) and *average fees (purple)*. All of these data can be shown with daily precision by hovering the cursor above the chart.

**II. Accounts:**

The two major data points that we found interesting on accounts are the number of daily active accounts and newly created accounts.&#x20;

Both of these data points are reflective of the general trends in usage and onboarding of developers and users towards the ecosystem. Detail number daily can be seen by hovering over the charts.

<figure><img src="/files/vvbaWsFrwK8vq4cHgjyc" alt=""><figcaption></figcaption></figure>

**III. Coins and Tokens:**

Another data point to keep track of for general usage and ínsights is the utilization and proliferation of on-chain coins and tokens, which could be seen through the chart below, with the data update regularly by the minute.

<figure><img src="/files/EkO9RE9iZNWCgelqCQO0" alt=""><figcaption></figcaption></figure>

IV. Top Ranking:

The top-ranking section goes beyond the surface, and let analysts take a closer look at the economic activities on Aptos, and its distribution.&#x20;

<figure><img src="/files/3z6lQRqZN6thwV3eUPlZ" alt=""><figcaption></figcaption></figure>

A few caveats here:

**Daily Active Modules**: refer to smart contract programs that initiated a transaction at least once a day.

**Top 100 Modules Ranking**: monitoring the concentration of economic activities by smart contract interactions (transactions) on the network

<figure><img src="/files/1SyEOzFy36ytuLYNia2a" alt=""><figcaption></figcaption></figure>

**Modules by Total Transaction**: Percentage chart of the top modules on the Aptos Network

**Interacted function rankings:**  top function usage on the network.&#x20;


---

# 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.aptscan.ai/browsing-the-site/analytics/aptos-network.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.