# Base Chain Stats: Transactions, Users and Fees

> Base chain stats by day: transactions, active addresses, fees users paid, fee vault revenue and blob costs paid to Ethereum, beside Arbitrum and OP Mainnet.

Markdown copy of https://voltfincrypto.com/apps/base-chain-stats

**Question:** How many transactions, active addresses and fees does Base process each day?

- Kind: Dashboard in Voltfin Vantage
- Topic: [Layer 2s](https://voltfincrypto.com/topics/layer-2)
- Chains: Base, Ethereum, Arbitrum, OP Mainnet
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

Base is an Ethereum layer 2 built on the OP Stack and incubated by Coinbase, which runs its sequencer. This dashboard follows its activity day by day: transactions, active addresses, the fees users paid and what Base paid Ethereum to post its data, all read from Base's blocks and from Ethereum.

Fees on Base land in fee vaults: one for the base fee, one for priority fees, one for the L1 data fee and one for operator fees. Reading those vaults, and the blob transactions Base sends to Ethereum, shows what the chain collects and what it spends, without relying on anyone's reported figures.

Use it to follow Base's growth, to explain a spike in activity or to check what the chain collects against what it spends. A comparison table puts Base beside Arbitrum and OP Mainnet on the same definitions, so activity and fees compare fairly.

## Blueprint

### Activity

Transactions, active addresses and fees on Base by day, beside Arbitrum and OP Mainnet.

- **Transactions, latest day** (count): Transactions in Base blocks on the latest complete UTC day, leaving out the system deposit that opens each block.
- **Active addresses, latest day** (count): Distinct addresses that sent at least one transaction on Base on the latest complete UTC day.
- **Fees users paid, latest day** (ETH): Fees paid on Base on the latest complete day: execution fees plus L1 data and operator fees, from receipts.
- **Median transaction fee** (USD): The median fee paid per transaction on Base on the latest complete day.
- **Transactions and active addresses by day** (count): Daily transactions and daily active addresses on Base over the selected period.
- **Base, Arbitrum and OP Mainnet**: For each of the three chains over the selected period: daily transactions, active addresses, fees users paid and costs paid to Ethereum, on the same definitions.

### Revenue and costs

What Base collects in its fee vaults and what it pays Ethereum.

- **Fee vault revenue, 30 days** (ETH): Fees collected by Base's four fee vaults over the last 30 days.
- **Paid to Ethereum, 30 days** (ETH): Gas and blob fees of Base's batcher and proposer transactions on Ethereum over the last 30 days.
- **Revenue and costs by day** (ETH): Daily fee vault revenue beside daily Ethereum costs, with the margin between them.
- **Ethereum costs by kind** (ETH): What Base paid Ethereum each day, split into blob fees, gas for batch transactions and gas for dispute game transactions.

Filters: Period (Last week, month, quarter or year).

## How it will be measured

- Transactions and active addresses are counted from Base blocks per UTC day, leaving out the L1 attributes deposit that opens each block; an address is active on a day when it sends at least one transaction.
- Fees users paid are gas_used times effective_gas_price plus the l1Fee and operator fee in each receipt. Base does not burn its base fee: it is paid into the BaseFeeVault predeploy.
- Revenue is read from the SequencerFeeVault, BaseFeeVault, L1FeeVault and OperatorFeeVault predeploys, as their balances at day-end blocks plus their withdrawals.
- Costs paid to Ethereum are the gas and blob fees of Base's batcher transactions to its batch inbox and of its proposer's dispute game transactions, read from Ethereum receipts.
- Every figure names the Base or Ethereum block it was read at, with the block hash and the read.

## 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.
- `l2_activity_daily` (to build): Per layer 2 per day: transactions, active addresses, fees users paid on the L2, and what the L2 paid Ethereum to settle and post data.
- `blob_usage_daily` (to build): EIP-4844 blobs posted per day, blob gas used, blob base fee, and the rollup that posted them.
- `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: Base blocks, transactions and receipts: gas_used, effective_gas_price, l1Fee and operator fee
- Source: Distinct senders per day on Base
- Source: Balances and withdrawals of the SequencerFeeVault, BaseFeeVault, L1FeeVault and OperatorFeeVault predeploys
- Source: Base batcher blob transactions to its batch inbox on Ethereum, with blob fees from receipts
- Source: Dispute game transactions of the Base proposer on Ethereum
- Source: Chainlink ETH/USD at day-end blocks

## Questions

### How many transactions does Base process per day?

The dashboard counts every transaction in Base blocks each UTC day, leaving out the system deposit that opens each block. It shows the latest complete day with its block range, and the history chart shows how the daily count has moved.

### Does Base burn fees?

No. On OP Stack chains the base fee is paid into a fee vault instead of being burned as it is on Ethereum. Base's vaults collect the base fee, priority fees, the L1 data fee and any operator fee. The operator then withdraws them to Ethereum.

### How much does Base pay Ethereum?

Base posts its transaction data to Ethereum in blobs and proposes its state through dispute games. The dashboard sums the gas and blob fees of those Ethereum transactions each day, so the cost can be set against the fees Base collected.

### Who runs Base?

Base was incubated by Coinbase, which operates its sequencer: the node that orders transactions and builds blocks. Withdrawals to Ethereum rest on the OP Stack's fault proofs, in which anyone can challenge an incorrect state claim.

### How does Base compare with Arbitrum?

The comparison table shows Base, Arbitrum and OP Mainnet on the same definitions: transactions, active addresses, fees users paid and costs paid to Ethereum. Each chain's system transactions are left out the same way, so the counts compare.

## Glossary

- **Sequencer**: The node that orders a layer 2's transactions and builds its blocks.
- **Fee vault**: A predeploy contract on an OP Stack chain that collects one kind of fee until it is withdrawn.
- **Batch inbox**: The Ethereum address a rollup's batcher sends its transaction data to, carried in blobs or calldata.

## Related apps

- [Ethereum L2 Fees Compared: Cost per Transaction](https://voltfincrypto.com/apps/ethereum-l2-fees)
- [L2 Profitability: Fees Earned vs Costs Paid to Ethereum](https://voltfincrypto.com/apps/l2-profitability)
- [Stablecoins on Base: Supply and Transfers](https://voltfincrypto.com/apps/stablecoins-on-base)
- [Ethereum Layer 2 List Ranked by Activity, Fees and Value](https://voltfincrypto.com/apps/ethereum-layer-2-list)
- [Ethereum TPS: Mainnet and Layer 2 Transactions per Second](https://voltfincrypto.com/apps/ethereum-tps)
- [LayerZero DVN Checker: Bridge Verifier Settings](https://voltfincrypto.com/apps/layerzero-dvn-checker)

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