Dashboard · VantagePlanned

Sonic Network Stats: Transactions, Fee Monetization and S Staked

How is Sonic used, and where do the fees its users pay end up?

Sonic by day: transactions, active addresses, new contracts, Gateway flows and how fees split between apps, validators and the burn.

ShareEmail itvoltfincrypto.com/apps/sonic-network-stats
Blueprint

What the dashboard will show.

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.

Activity

Transactions, active addresses, new contracts and Gateway flows.

Transactions, latest day

count

Transactions in Sonic blocks on the latest complete UTC day, successful and failed.

Figurechain_activity_dailyAwaiting data

Active addresses, latest day

count

Distinct senders of successful transactions on the latest complete day.

Figurechain_activity_dailyAwaiting data

New contracts, latest day

count

Contracts created on the latest complete day, from create and create2 calls in traces.

Figurechain_activity_dailyAwaiting data

Gateway net flow, latest day

USD

Value bridged into Sonic through the Sonic Gateway minus value bridged out on the latest complete day.

Figurebridge_flows_dailyAwaiting data

Transactions and active addresses by day

count

Daily transactions and distinct senders since mainnet, so lasting use can be told apart from bursts around incentive campaigns.

Line chartchain_activity_dailyAwaiting data

Fees and staking

Fees paid and how they split between apps, validators and the burn, with S staked.

Fees paid, latest day

S

Fees paid on the latest complete day: gas used times effective gas price, in S.

Figurechain_fees_dailyAwaiting data

Paid to apps through FeeM

S

The part of the latest complete day's fees paid to apps registered in Fee Monetization.

Figureprotocol_revenue_dailyAwaiting data

S burned, latest day

S

The part of the latest complete day's fees that was burned.

Figurechain_fees_dailyAwaiting data

S staked

S

S staked with validators, self-stake and delegations together, at the latest day-end block.

Figurestaking_networks_dailyAwaiting data

Where fees went by day

S

Fees each day over the selected period, split into apps through Fee Monetization, validators and the burn.

Stacked barschain_fees_dailyAwaiting data

Period
Last 30 days, 90 days or since mainnet
About

What it answers, and for whom.

Sonic is an EVM layer 1 that succeeded Fantom in December 2024, with S as its gas and staking token. This dashboard reads every Sonic block to show how the chain is used, from transactions, active addresses and new contracts to the value moving through the Sonic Gateway. It also shows where users' fees end up, beside the S staked by its validators.

Fees on Sonic do not all go to one place. Through Fee Monetization, apps can earn a share of the fees their users pay, validators take a share and part is burned, under rules that governance has changed since launch. The dashboard reads each part from the contracts that pay it, so the split shown is the one that happened. Every figure is pinned to its block, with a receipt.

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 →
  1. Transactions, active addresses and new contracts are counted from every Sonic block per UTC day, with the same rules as on other EVM chains.
  2. Fees are gas used times the effective gas price; the split between apps, validators and the burn is read from the Fee Monetization contracts and the fee distribution recorded on-chain, never assumed from a fixed rule, since governance has changed it.
  3. S staked and validators come from the SFC staking contract at the day's last block: each validator's self-stake and the delegations to it.
  4. Gateway flows are deposits and withdrawals through the Sonic Gateway on both sides, and every figure carries a receipt with the block number and hash.

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.
  • chain_fees_dailyTo buildFees and gas by chainFees 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.
  • protocol_revenue_dailyTo buildProtocol fees, revenue and buybacksFees users paid to each protocol and the part kept by the protocol or its token holders, per protocol and day, including buybacks.
  • staking_networks_dailyTo buildProof-of-stake networksStaked supply, staking ratio, validators and nominal rewards per proof-of-stake network per day.
  • bridge_flows_dailyTo buildBridge deposits and withdrawalsDeposits into and withdrawals out of canonical and major third-party bridges by chain, token and day, plus escrow balances at day end.
  • Sonic block headers and transactions: gas used, effective gas price, sender and status
  • Execution traces: create and create2 calls, for new contracts
  • Fee Monetization contracts: registered projects, the fees attributed to each and the rewards paid
  • SFC staking contract state at day-end blocks: validators, self-stake and delegations
  • Sonic Gateway deposit and withdrawal events on Ethereum and on Sonic
Questions

Questions people ask.

What is Sonic?

An EVM-compatible layer 1 launched in December 2024 by the team behind Fantom, which it replaced: FTM holders could upgrade to S, Sonic's native token. It is built for fast finality, and S pays for gas and is staked by validators.

What is Sonic Fee Monetization?

A program that pays apps a share of the gas fees their users generate. Apps register their contracts and earn a share set by governance rules; the rest of each fee goes to validators or is burned. The dashboard reads what was paid to apps from the program's contracts each day.

How much of Sonic's fees are burned?

It depends on the transaction and on the rules in force. Fees from apps in Fee Monetization are mostly shared between the app and validators, while other fees are partly burned. The rules have been revised since launch, so the fee split chart shows what actually went to apps, validators and the burn each day.

What is the Sonic Gateway?

Sonic's native bridge to Ethereum. Deposits and withdrawals settle in batches, and a fail-safe lets users reclaim bridged assets on Ethereum if the gateway stops working for an extended period. The activity page shows the value moving through it each day.

How does staking S work?

Validators lock S in the staking contract and holders delegate to them, sharing in the rewards. Unstaking takes a waiting period before tokens can be withdrawn. Total stake and its spread across validators show how much S secures the network.

S
Sonic's native token, used for gas and staking; FTM holders could upgrade to it when Sonic replaced Fantom.
Fee Monetization
Sonic's program that pays registered apps a share of the gas fees their transactions generate.
SFC
The special fee contract, Sonic's built-in staking contract that records validators, delegations and rewards.
Sonic Gateway
Sonic's native bridge to Ethereum, with a fail-safe that lets users recover bridged assets on Ethereum if it stops.

Build Sonic Network Stats: Transactions, Fee Monetization and S Staked 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.