Avalanche C-Chain Stats: Transactions, Gas and AVAX Burned
Avalanche C-Chain use by day: transactions, active addresses, block time and base fee, with the AVAX its fees burn and the AVAX staked.
AvalancheTable · StrataPlanned
Avalanche L1 Tracker: Chains, Validators and Activity
Which Avalanche L1s are live, and how active is each one?
Every Avalanche L1 the P-Chain records, with its validators, their fee balances, its gas token and how active its chain is each day.
ShareEmail it
Blueprint
What the table will hold.
The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
One row One row per Avalanche L1 or legacy subnet chain, on the latest complete UTC daySorted by Transactions, latest day, highest first
| L1 | Type | Created | Validator management | Validators | Validator fee balanceAVAX | Gas token | Transactions, latest day | Active addresses | ICM messages | Receipt |
|---|---|---|---|---|---|---|---|---|---|---|
- L1 l1 Text
- The chain's name as registered on the P-Chain, linked to its blockchain ID.
- Type type Text
- L1, if converted under ACP-77, or legacy subnet, whose validators also validate the Primary Network.
- Created created Date
- The date of the CreateChainTx that registered the chain on the P-Chain.
- Validator management validator_management Text
- How validators are chosen: proof of authority or proof of stake through the L1's validator manager contract, or legacy subnet rules.
- Validators validators Number
- Active validators of the chain at the day's last P-Chain block.
- Validator fee balance fee_balance Exact amount
- AVAX left in the chain's validators' P-Chain balances to pay the continuous L1 validator fee; empty for legacy subnets.
- Gas token gas_token Token
- The native token the chain charges gas in, from its genesis configuration.
- Transactions, latest day transactions Number
- Transactions in the chain's blocks on the latest complete UTC day; empty where no public endpoint exists.
- Active addresses active_addresses Number
- Distinct senders of successful transactions on the latest complete day.
- ICM messages icm_messages Number
- Interchain messages the chain sent or received on the latest complete day.
- Receipt receipt Link
- The P-Chain and L1 blocks and the reads behind the row.
Filter by Type, Validator management.
About
What it answers, and for whom.
Avalanche L1s are blockchains registered on Avalanche's P-Chain that run their own validators, gas tokens and rules: game networks, exchanges, payment chains and enterprise chains among them. This table lists every one the P-Chain records, with when it was created, how its validators are managed, how many it has, the gas token it uses and how active its chain was on the latest complete day.
Since the Avalanche9000 upgrade of December 2024, an L1's validators no longer need to validate the Primary Network or stake AVAX there. Each pays a continuous fee from a balance it keeps on the P-Chain instead, so the table shows those balances as well. Sort it by activity or validators, filter it by type and open any row to see the P-Chain and L1 blocks behind it.
Method
How it will be measured.
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 →- The registry is read from the P-Chain: CreateSubnetTx and CreateChainTx for every subnet and chain, and ConvertSubnetToL1Tx for those converted to L1s under ACP-77, with the date and block of each.
- Validators and fee balances come from the P-Chain's L1 validator records, built from RegisterL1ValidatorTx, IncreaseL1ValidatorBalanceTx, SetL1ValidatorWeightTx and DisableL1ValidatorTx, at the day's last P-Chain block.
- Activity is read from each L1's own blocks through its public RPC endpoint: transactions and distinct senders per UTC day. An L1 with no public endpoint keeps its registry row with activity left empty, never zero.
- Interchain messages count the ICM messages each L1 sent and received in the day, from the messenger contract's events on its chain.
- Every row names the P-Chain block and the L1 block its figures were read at.
The data it needs
Read from chain state and history
- chain_activity_dailyTo buildChain activity by dayTransactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions.
- staking_networks_dailyTo buildProof-of-stake networksStaked supply, staking ratio, validators and nominal rewards per proof-of-stake network per day.
- P-Chain transactions: CreateSubnetTx, CreateChainTx and ConvertSubnetToL1Tx, for the registry
- P-Chain L1 validator transactions: RegisterL1ValidatorTx, IncreaseL1ValidatorBalanceTx, SetL1ValidatorWeightTx and DisableL1ValidatorTx
- platform.getCurrentValidators per subnet ID and platform.getValidatorFeeState at day-end P-Chain blocks, for validators and balances
- Each L1's EVM blocks through its RPC endpoint: transaction count, gas used and senders
- ICM messenger contract events on each L1: messages sent and received
Questions
Questions people ask.
What is an Avalanche L1?
A blockchain with its own validators, gas token and rules that is registered on Avalanche's P-Chain; L1s used to be called subnets. Since the Avalanche9000 upgrade, an L1's validators need not validate the Primary Network or stake AVAX there, and pay a continuous fee to the P-Chain instead.
What is the difference between a subnet and an L1?
A legacy subnet's validators must also validate Avalanche's Primary Network, which requires staking AVAX there. A subnet converted to an L1 under ACP-77 manages its validators through a contract on its own chain, and each validator keeps an AVAX balance on the P-Chain that pays its fee second by second.
What happens when an L1 validator's balance runs out?
The fee is drawn from the balance continuously. A validator whose balance reaches zero is deactivated until someone tops it up with an IncreaseL1ValidatorBalanceTx, so the remaining balance shows how long an L1's validators can run without a top-up.
Are Avalanche L1s secured by AVAX?
Not directly. Each L1 chooses its validators and its rules for joining, which can be proof of authority or proof of stake in its own token. AVAX pays the P-Chain fee, and Avalanche Warp Messaging lets chains verify each other's messages through their validators' signatures.
Why are some activity columns empty?
Activity is read from each L1's own blocks, which needs a public endpoint. L1s that keep their chains private, as some enterprise chains do, appear with their P-Chain registry data and empty activity columns, because missing data is never shown as zero.
- Avalanche L1
- A blockchain registered on Avalanche's P-Chain with its own validator set, gas token and rules; formerly called a subnet.
- ACP-77
- The Avalanche Community Proposal, activated with Avalanche9000, that lets L1s manage their own validators, who pay a continuous fee instead of staking on the Primary Network.
- Validator manager
- The contract on an L1 that decides who validates it, by proof of authority or proof of stake, and reports changes to the P-Chain through Warp messages.
- Interchain Messaging (ICM)
- Avalanche's protocol for sending messages and tokens between L1s and the C-Chain, verified with the sending chain's validator signatures.
Related
More apps like this.
Layer 1 Blockchain List: Activity, Fees and Staking
Major layer 1 chains in one sortable table: transactions, active addresses, fees, block time, validators, staked share and mainnet date.
Multi-chainBitcoinEthereum+13Validator Count and Nakamoto Coefficient by Chain
Proof-of-stake validator sets side by side: active validators, any cap on the set, how validators join and the Nakamoto coefficient.
Multi-chainEthereumSolana+13Blockchain Games Ranked by Daily Active Wallets
On-chain games sorted by the distinct wallets playing each day, with transactions, new players and in-game asset trades beside them.
Multi-chainSmart Contract Deployments by Chain: New Contracts per Day
New contracts per day on each chain, counted apart for EVM contracts, Solana programs and Move packages, with deployers and factory share.
Multi-chainEthereumBase+14Chainlink CCIP Tracker: Cross-Chain Messages and Token Transfers
Messages and token value sent over Chainlink CCIP lane by lane, with delivery times, fee tokens and how close pools are to their limits.
Multi-chainEthereumArbitrum+5Build Avalanche L1 Tracker: Chains, Validators and Activity on verified data.
Start 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.