# Solana Network Stats: TPS, Fees and Active Wallets > Solana network stats each day: non-vote TPS, daily transactions, fees in SOL and USD, active wallets, the failed share and skipped slots, from every block. Markdown copy of https://voltfincrypto.com/apps/solana-network-stats **Question:** How many transactions, fees and active wallets does Solana process each day? - Kind: Dashboard in Voltfin Vantage - Topic: [Solana](https://voltfincrypto.com/topics/solana) - Chains: Solana - Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is. Solana produces a block in each slot, a fraction of a second apart, and every block records its transactions, the fees they paid and whether they succeeded. This dashboard reads them to show how Solana is used each day: throughput, transactions, fees in SOL and USD, distinct fee-paying wallets, the share of transactions that failed and the slots their leaders skipped. Read the counts with Solana's history in mind. Until the Alpenglow upgrade, validators' consensus votes were transactions too, and they made up much of the raw count; this dashboard counts user transactions throughout and shows the former vote traffic apart. Every figure is pinned to the slot it was read at, with the block hash and a receipt. ## Blueprint ### Today Throughput, transactions, wallets and failures over time. - **Non-vote TPS, last 24 hours** (tx per second): Non-vote transactions over the last 24 hours divided by the seconds the period's blocks span. - **Transactions, latest day** (count): Non-vote transactions in blocks of the latest complete UTC day, successful and failed. - **Active wallets, latest day** (count): Distinct fee payers of successful non-vote transactions on the latest complete day. - **Failed share** (%): Non-vote transactions whose meta.err is set, as a share of all non-vote transactions on the latest complete day. - **Transactions by day** (count): Successful and failed non-vote transactions per day, with the vote transactions blocks carried before the Alpenglow upgrade shown apart. - **Active wallets by day** (count): Distinct fee-paying wallets per day and over rolling 30 days. - **Skipped slots by epoch** (%): Leader slots without a block as a share of all leader slots in each epoch, from getBlockProduction. ### Fees Fees paid in SOL and USD, base and priority. - **Fees paid, latest day** (SOL): Fees paid on the latest complete day in SOL, base and priority fees together, from each transaction's meta.fee. - **Fees paid in USD** (USD): The same day's fees valued at the SOL/USD oracle price at the day's last block. - **Base and priority fees by day** (SOL): Base fees and priority fees paid per day in SOL, which shows how much users bid for priority. Filters: Period (Last week, month, quarter or year). ## How it will be measured - Blocks are read with getBlock for every slot: block time, transactions, fees and status, rolled up per UTC day and kept per slot for recent hours. - Non-vote transactions exclude those that call the Vote program, which carried validators' consensus votes before the Alpenglow upgrade; that former vote traffic is shown on its own series. - Fees come from each transaction's meta.fee in lamports, split into the base fee for its signatures and the priority fee, with compute from meta.computeUnitsConsumed. - Active wallets are distinct fee payers, the first signer, of successful non-vote transactions per day and per 30 days; the failed share counts transactions whose meta.err is set. - Skipped slots come from getBlockProduction per epoch and USD values from an on-chain SOL/USD oracle feed at the day's last block. Each figure carries a receipt. ## 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. - `native_prices_daily` (to build): Reference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time. - Source: getBlock per slot: blockTime and transactions, with meta.fee, meta.err and meta.computeUnitsConsumed - Source: Vote program (Vote111111111111111111111111111111111111111) instructions, to separate vote transactions - Source: The first signer of each non-vote transaction, for distinct fee payers per day and per 30 days - Source: getBlockProduction per epoch: leader slots and blocks produced - Source: An on-chain SOL/USD oracle feed at each day's last block, for USD fee totals ## Questions ### How many transactions per second does Solana process? The dashboard measures it from blocks: the non-vote transactions of the last 24 hours divided by the seconds their blocks span. That is what users actually sent, which reflects demand rather than the network's capacity. ### What are Solana vote transactions? Under Solana's original consensus, validators sent their votes on each block as transactions, which made up a large share of all transactions. The Alpenglow upgrade moved voting out of the ledger, so the dashboard counts user transactions throughout and shows the former vote traffic apart. ### Why do so many Solana transactions fail? Much of it comes from bots: arbitrage and trading programs send many transactions knowing that only some will succeed, because a failed transaction is cheap. A failed transaction still pays its fee. The failed share shows how much of the traffic is such attempts. ### How are Solana fees calculated? Each transaction pays a fixed base fee for each signature, half of which is burned, plus an optional priority fee set as a price per compute unit, which goes to the block's leader. The dashboard shows both parts and the fee per transaction. ### What is a skipped slot? A slot in which the scheduled leader did not produce a block, because it was offline or late or its block did not reach the rest of the network. Skipped slots delay transactions and cost the leader the fees that block would have earned. ## Glossary - **Slot**: Solana's unit of time, in which one scheduled leader may produce a block. - **Lamport**: The smallest unit of SOL, one billionth of a coin; fees are quoted in lamports. - **Fee payer**: The first signer of a Solana transaction, who pays its fee; used here to count active wallets. - **Compute unit**: Solana's measure of the computation a transaction uses; priority fees are priced per compute unit. - **Epoch**: A period of slots, about two days long, at which stake, the leader schedule and rewards are updated. ## Related apps - [Solana Priority Fee Tracker](https://voltfincrypto.com/apps/solana-priority-fee-tracker) - [Solana Validator Count and Stake Concentration](https://voltfincrypto.com/apps/solana-validator-count) - [Solana Staking Yield (APY) and SOL Staked](https://voltfincrypto.com/apps/solana-staking-yield) - [Stablecoins on Solana: Supply by Coin](https://voltfincrypto.com/apps/stablecoins-on-solana) - [Pump.fun Token Launches and Graduations per Day](https://voltfincrypto.com/apps/pump-fun-token-launches) - [Solana vs Ethereum: Fees, Activity and Revenue](https://voltfincrypto.com/apps/solana-vs-ethereum) Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F