User transactions, latest day
countUser transactions on the latest complete UTC day, leaving out block metadata, block epilogue and validator transactions.
How many user transactions does Aptos process, and how much APT does gas burn?
Aptos by day: user transactions apart from protocol ones, senders, first-time senders and throughput, with APT burned as gas and APT staked.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
User transactions, senders, first-time senders and throughput.
User transactions on the latest complete UTC day, leaving out block metadata, block epilogue and validator transactions.
Distinct accounts that sent user transactions on the latest complete day.
Accounts that sent their first user transaction on the latest complete day.
The latest complete day's user transactions divided by the seconds its blocks span.
User transactions and distinct senders by day over the selected period, with protocol transactions shown as a separate line.
APT burned as gas, storage deposits net of refunds and APT staked.
Gas fees burned on the latest complete day: gas used times gas unit price for every user transaction, in APT.
Storage fees charged for new state minus refunds for deleted state on the latest complete day.
APT staked with active validators at the latest epoch boundary, from the validator set.
Validators in the active set at the latest epoch boundary.
Gas burned, storage deposits charged and storage refunds each day over the selected period, with refunds shown below zero.
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.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Read from chain state and history
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.
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.
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.
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.
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.
Sui by day: transactions, senders and throughput from checkpoints, gas split into computation, storage and rebates, with the SUI staked.
SuiSui and Aptos compared each month on one set of definitions: user transactions, senders, fees on each chain's model, stake and stablecoins.
SuiAptosGross staking yield, yield after supply growth and the share of supply staked on each proof-of-stake chain, from on-chain rewards.
Multi-chainEthereumSolana+12Major layer 1 chains in one sortable table: transactions, active addresses, fees, block time, validators, staked share and mainnet date.
Multi-chainBitcoinEthereum+13Transactions per second each chain actually processed, measured from its blocks over the last hour and day, with peaks and block times.
Multi-chainSolanaBNB Chain+5New contracts per day on each chain, counted apart for EVM contracts, Solana programs and Move packages, with deployers and factory share.
Multi-chainEthereumBase+14Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.