# Aptos Network Stats: User Transactions, Gas and APT Staked

> Aptos network stats by day: user transactions, active accounts, first-time senders and TPS, plus APT burned as gas, net storage deposits and APT staked.

Markdown copy of https://voltfincrypto.com/apps/aptos-network-stats

**Question:** How many user transactions does Aptos process, and how much APT does gas burn?

- Kind: Dashboard in Voltfin Vantage
- Topic: [Layer 1 chains](https://voltfincrypto.com/topics/chains)
- Chains: Aptos
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

Aptos is a layer 1 built on the Move language that executes each block's transactions in parallel. This dashboard reads every block to show how the chain is used each day, from user transactions, distinct senders and first-time senders to throughput, together with the APT burned as gas, net storage deposits and the APT staked with validators.

Aptos writes protocol transactions into every block next to users' ones, so a count of ledger versions overstates usage; the dashboard counts user transactions and keeps the rest apart. Gas is burned, while storage is a refundable deposit, and both are read from each transaction's fee statement. Every figure names the block and ledger version it came from, with a receipt.

## Blueprint

### Activity

User transactions, senders, first-time senders and throughput.

- **User transactions, latest day** (count): User transactions on the latest complete UTC day, leaving out block metadata, block epilogue and validator transactions.
- **Active accounts, latest day** (count): Distinct accounts that sent user transactions on the latest complete day.
- **First-time senders, latest day** (count): Accounts that sent their first user transaction on the latest complete day.
- **Average TPS, latest day** (tx per second): The latest complete day's user transactions divided by the seconds its blocks span.
- **User transactions and senders by day** (count): User transactions and distinct senders by day over the selected period, with protocol transactions shown as a separate line.

### Gas and staking

APT burned as gas, storage deposits net of refunds and APT staked.

- **APT burned as gas, latest day** (APT): Gas fees burned on the latest complete day: gas used times gas unit price for every user transaction, in APT.
- **Storage deposits, net** (APT): Storage fees charged for new state minus refunds for deleted state on the latest complete day.
- **APT staked** (APT): APT staked with active validators at the latest epoch boundary, from the validator set.
- **Active validators** (count): Validators in the active set at the latest epoch boundary.
- **Gas and storage by day** (APT): Gas burned, storage deposits charged and storage refunds each day over the selected period, with refunds shown below zero.

Filters: Period (Last 30 days, 90 days or a year).

## How it will be measured

- Only user transactions count as activity: the block metadata, block epilogue and validator transactions that the protocol writes into blocks are counted apart, so the ledger's version count never stands in for usage.
- Gas burned is gas used times gas unit price for each user transaction, converted from octas to APT; Aptos burns gas fees rather than paying them to validators.
- Storage deposits and refunds come from each transaction's FeeStatement event: the fee charged for new state slots and bytes, and what was refunded when slots were deleted.
- APT staked and validators come from the validator set at each epoch boundary, and every figure carries a receipt with the ledger version and block height it was read at.

## Data it needs

- `chain_activity_daily` (to build): Transactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions.
- `chain_fees_daily` (to build): Fees paid per chain per day in the native token: base fee and priority fee percentiles, total fees, and the share burned where the chain burns fees.
- `staking_networks_daily` (to build): Staked supply, staking ratio, validators and nominal rewards per proof-of-stake network per day.
- Source: Aptos transactions by ledger version, with type: user, block metadata, block epilogue (formerly state checkpoint) and validator transactions
- Source: User transaction info: sender, fee payer, success, gas_used and gas_unit_price
- Source: FeeStatement events: execution, IO and storage gas, storage_fee_octas and storage_fee_refund_octas
- Source: The validator set in 0x1::stake at each epoch boundary: active validators and their voting power

## Questions

### How many transactions does Aptos process?

The dashboard counts user transactions, those signed and submitted by accounts. Every Aptos block also holds transactions the protocol writes itself, such as block metadata, which inflate a raw count of ledger versions. They are shown apart so the user count stays comparable with other chains.

### Are Aptos gas fees burned?

Yes. The gas a transaction pays, gas used times its gas unit price, is burned, and validators are paid from staking rewards instead of fees. The storage deposit for new state is handled separately and can be refunded when that state is deleted.

### What is the storage fee on Aptos?

A charge for each new item a transaction adds to on-chain state, priced in APT rather than gas so it does not swing with gas prices. When the item is later deleted, the deposit for its slot is refunded to the transaction's payer. The dashboard shows deposits and refunds by day.

### Why does Aptos run transactions in parallel?

Aptos executes each block with Block-STM, which runs transactions at the same time and re-runs any that conflict, so the result matches running them in order. Throughput therefore depends on how often a block's transactions touch the same accounts and resources.

### How does APT staking work?

Validators stake APT in stake pools, and holders can delegate to them through delegation pools. Rewards come from new issuance and are paid at the end of each epoch, and stake that is unlocked becomes withdrawable when the pool's lockup cycle ends. The staking tiles read the validator set at every epoch boundary.

## Glossary

- **User transaction**: A transaction signed and submitted by an account, as opposed to the block metadata and epilogue transactions the protocol writes itself.
- **Octa**: The smallest unit of APT, in which gas prices and fees are recorded on-chain.
- **Block-STM**: Aptos's parallel execution engine: it runs a block's transactions at once and re-executes those that conflict, matching the result of running them in order.
- **Fungible asset**: Aptos's token standard that replaces the older coin standard; stablecoins on Aptos are issued as fungible assets.
- **Fee payer**: An account that pays the gas for another account's transaction, which lets apps sponsor their users' fees.

## Related apps

- [Sui Network Stats: Transactions, Gas Fees and SUI Staked](https://voltfincrypto.com/apps/sui-network-stats)
- [Sui vs Aptos: Activity, Fees and Staking Compared](https://voltfincrypto.com/apps/sui-vs-aptos)
- [Staking Yield and Staking Ratio by Chain](https://voltfincrypto.com/apps/staking-yield-by-chain)
- [Layer 1 Blockchain List: Activity, Fees and Staking](https://voltfincrypto.com/apps/layer-1-blockchain-list)
- [Blockchain TPS Tracker: Measured Throughput by Chain](https://voltfincrypto.com/apps/blockchain-tps-tracker)
- [Smart Contract Deployments by Chain: New Contracts per Day](https://voltfincrypto.com/apps/smart-contract-deployments-by-chain)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F