Validators process transactions and receive fees from users (supply-side fees).

Ronin is a smart contract platform for decentralized applications (a blockchain). Ronin was founded by Sky Mavis and launched in 2021.

RON holders own and govern the protocol. They currently don’t take a cut of the total transaction fees paid by users (revenue). Sky Mavis' investors include a16z, Binance, Animoca Brands, etc.

github

twitter

discord

website

Blockchains (L1)

Ronin

# Ronin Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Ronin blockchain over a daily period. This metric answers the question "What is the daily average transaction throughput capacity and usage of the Ronin network?" The calculation takes the total number of unique transactions in a day and divides by 86,400 seconds to provide a standardized throughput measure.

## 2. Data sources

- **Ronin blockchain transaction records**: Raw transaction data from the Ronin blockchain including block timestamps, transaction hashes, sender/receiver addresses, gas usage, and gas prices
- **RON token metadata**: The native RON token contract address (`0xe514d9deb7966c8be0ca922de8a064264ea6bcd4`) used for standardizing gas price calculations
- **Chain availability configuration**: Metadata defining when the Ronin chain was operational and available for transaction processing

## 3. Step-by-step calculation

### Component A: Transaction fact table creation
- **Purpose**: Standardize and clean raw Ronin transaction data for downstream processing
- **Logic**: Raw Ronin blockchain transaction records are transformed by safely casting timestamps to proper timestamp format, converting block numbers to integers, and standardizing transaction hashes and addresses to strings. Gas usage is converted from the raw receipt values to proper numeric format, while gas prices are normalized from wei to RON by dividing by 10^18. The RON token address is attached to each record for standardization.
- **Key fields**: `block_timestamp` (transaction timing), `transaction_hash` (unique identifier), `from_address` and `to_address` (transaction participants), `gas_used` (computational cost), `effective_gas_price` (RON-denominated price)

### Component B: Daily transaction counting
- **Purpose**: Aggregate unique transactions by day while maintaining proper categorization
- **Logic**: Transaction timestamps are truncated to daily granularity using day-level timestamp truncation. Transactions are grouped by the truncated daily timestamp, chain identifier, market sector classification, and business segment. For each day, distinct transaction hashes are counted to avoid double-counting any duplicate records. Missing dates are identified and filled with zero transaction counts to maintain a continuous daily time series.
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct daily transaction total), `chain_id` ('ronin'), `market_sector_id` ('blockchains_l1'), `business_segment_id` ('blockchain')

### Final aggregation
- **Combining components**: Daily transaction counts from Component B are used as input for the TPS calculation
- **Currency conversion**: No currency conversion required as this is a count-based metric
- **Time aggregation**: Data is already aggregated at daily boundaries from the transaction counting step
- **Final calculation**: The transactions per second value is calculated by dividing the daily transaction count by 86,400 (the number of seconds in a day) using safe division to handle any edge cases. Schema validation ensures proper data types and structure, while chain availability filtering removes any data from periods when the Ronin chain was not operational or data was not reliably captured.

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Average confirmed user transactions added per second.

RoninRON

Archived

Transactions per second

Transactions per second

Competitive landscape