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 Transaction count Methodology

## 1. Overview

Transaction count measures the daily number of unique transactions executed on the Ronin blockchain. This metric quantifies network activity by counting distinct transaction hashes per day, providing insight into user engagement and network utilization. The calculation aggregates all transaction activity regardless of transaction type or value, focusing purely on transaction volume as an indicator of network usage.

## 2. Data sources

- **Ronin blockchain transaction records**: Complete transaction history from the Ronin blockchain including transaction hashes, block timestamps, sender and receiver addresses, gas usage, and gas prices
- **RON token metadata**: Hardcoded native token address (`0xe514d9deb7966c8be0ca922de8a064264ea6bcd4`) used for gas fee denomination and chain identification

## 3. Step-by-step calculation

### Component A: Transaction data extraction and standardization
- **Purpose**: Prepare raw Ronin transaction data for aggregation by standardizing data types and normalizing gas price units
- **Logic**: Extract transaction records from Ronin blockchain data including block timestamps, transaction hashes, sender and receiver addresses, gas usage, and gas prices. Cast all fields to appropriate data types ensuring data consistency. Normalize gas prices from wei units to RON units by dividing by 10^18 to convert from the smallest denomination to standard token units. Attach the hardcoded RON token address to identify the native token used for gas fees
- **Key fields**: `block_timestamp` for time-based aggregation, `transaction_hash` for unique transaction identification, `from_address` and `to_address` for transaction participants, `gas_used` and `effective_gas_price` for transaction cost analysis

### Component B: Daily transaction aggregation
- **Purpose**: Aggregate unique transactions by day and recipient address to generate daily transaction counts
- **Logic**: Truncate block timestamps to daily boundaries using day-level granularity to group transactions by calendar date. Count distinct transaction hashes within each day to avoid double-counting duplicate or resubmitted transactions. Group results by day, recipient address (`to_address`), and add standardized metadata including chain identifier as 'ronin', market sector as 'blockchains_l1' for Layer 1 blockchain classification, and business segment as 'blockchain'. Set product and contract name fields to null as this metric applies to the entire chain rather than specific protocols
- **Key fields**: Aggregated `transaction_count` representing unique daily transactions per recipient address, `timestamp` truncated to day boundaries, classification metadata for proper metric categorization

### Final aggregation
- **Combining components**: The daily aggregated data flows through a finalization macro that validates metric schema, ensures proper data typing, and applies gap-filling logic
- **Time continuity**: Apply 'fill_zeros' strategy to ensure continuous daily time series by inserting zero values for any missing dates in the time range, maintaining data continuity for visualization and analysis
- **Incremental processing**: Use incremental materialization with configurable lookback days to process only recent data updates while maintaining historical accuracy, reducing computation time for large datasets
- **Final calculation**: The metric represents the count of distinct transaction hashes per day, aggregated across all recipient addresses to provide total daily transaction volume for the Ronin blockchain. Chain availability filtering ensures only active chain periods are included in the final results.

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

Confirmed transactions added to the blockchain.

RoninRON

Archived

Transaction count

Transaction count

Competitive landscape