Fraxtal batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Fraxtal is an Ethereum Layer 2 (L2) blockchain built on the OP Stack by Frax Finance. It uses frxETH as the gas token and features a blockspace incentive system called Flox. Fraxtal launched in February 2024.

Frax Finance team owns and governs the protocol. Frax Finance's investors include Dragonfly Capital, Mechanism Capital, Galaxy Digital, etc.

twitter

discord

etherscan

website

Blockchains (L2)

Fraxtal

# Fraxtal Transactions per second Methodology

## 1. Overview

Transactions per second measures the average transaction throughput of the Fraxtal blockchain on a daily basis. This metric provides insight into network activity and processing capacity by reflecting the mean number of transactions processed per second across each 24-hour period. The total number of unique transactions in a day is divided by 86,400 seconds to produce an average value.

## 2. Data sources

- **Blockchain events**: Transaction records and gas usage data, covering Fraxtal

## 3. Step-by-step calculation

### Component A: Transaction data standardization

- **Purpose**: Clean and standardize raw Fraxtal transaction data for analysis
- **Logic**: Raw transaction records are processed to ensure consistent data types and formatting. Transaction timestamps are cast to proper timestamp format, transaction hashes are standardized as strings, and sender/recipient addresses are formatted consistently. A native gas asset address is assigned based on the North Star hardfork (April 29, 2025), where frxETH is identified for records prior to the fork and FRAX is assigned for subsequent records. Gas usage, L1 gas metrics, and gas prices are cast to numeric formats. A chain identifier of 'fraxtal' is added to distinguish this data from other blockchain networks
- **Key fields**: `block_timestamp` (when transaction was processed), `transaction_hash` (unique transaction identifier), `from_address` (sender), `to_address` (recipient), `token_address` (gas asset identifier), `gas_used` (gas consumed), `l1_gas_used` (L1 gas consumed), `l1_gas_price` (L1 gas price), `l1_fee_scalar` (L1 fee multiplier), `gas_price` (transaction gas price), `chain` (network identifier)

### Component B: Daily transaction counting

- **Purpose**: Aggregate transaction volume on a daily basis with proper metadata classification
- **Logic**: Transactions are grouped by day using timestamp truncation to create clean daily boundaries at midnight UTC. For each day, distinct transaction hashes are counted to avoid double-counting any transactions. The aggregation is performed separately for each recipient address to maintain granular tracking. Business metadata is added including chain classification as 'fraxtal', market sector as 'blockchains_l2' (Layer 2 blockchain), and business segment as 'blockchain'
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct transactions per address per day), `to_address` (recipient address), `chain_id` (fraxtal), `timestamp_grain` (day)

### Component C: TPS conversion calculation

- **Purpose**: Convert daily transaction counts to average transactions per second
- **Logic**: Daily transaction counts are summed across all recipient addresses to get the total network transaction volume for each day. This total is then divided by 86,400 (the number of seconds in a day) using safe division to handle any edge cases. An average TPS value is produced representing the mean transaction processing rate across the entire 24-hour period
- **Key fields**: `transactions_per_second` (final TPS metric), `timestamp` (daily boundary), `chain_id` (fraxtal)

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

Average confirmed user transactions added per second.

FraxtalFXTL

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown