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

## 1. Overview

The Fraxtal transaction count metric measures the daily number of unique transactions on the Fraxtal blockchain network. This metric provides insight into network activity and user engagement by counting distinct transactions per day, segmented by recipient address. The calculation aggregates raw transaction data from the Fraxtal blockchain into daily totals, applying Token Terminal's standardized metric schema for consistent cross-chain comparisons.

## 2. Data sources

- **Blockchain events**: Transaction records from the Fraxtal network, covering Fraxtal

## 3. Step-by-step calculation

### Component A: Transaction data preparation

- **Purpose**: Clean and standardize raw Fraxtal transaction data for analysis
- **Logic**: Extract transaction records from Fraxtal blockchain data, casting all fields to appropriate data types for consistency. The native gas asset is identified as frxETH prior to the North Star hardfork (April 29, 2025) and as FRAX thereafter. Gas price and usage metadata, including Layer 1 metrics, are also captured for each record. Add a chain identifier field set to "fraxtal" to enable cross-chain analysis. This component ensures data quality and standardization before aggregation.
- **Key fields**: `block_timestamp` (transaction timestamp), `transaction_hash` (unique transaction identifier), `from_address` (sender), `to_address` (recipient), `token_address` (native gas asset identification), `gas_price`, `gas_used`, `l1_gas_price`, `l1_gas_used`, `l1_fee_scalar`, `chain` (blockchain identifier)

### Component B: Daily transaction aggregation

- **Purpose**: Group transactions by day and recipient address to calculate daily transaction counts
- **Logic**: Truncate transaction timestamps to day boundaries to create consistent daily groupings. Group transactions by the truncated timestamp and recipient address (`to_address`). Count distinct transaction hashes within each group to avoid double-counting duplicate records. Apply standardized Token Terminal metadata including chain identifier ("fraxtal"), market sector ("blockchains_l2"), and business segment ("blockchain").
- **Key fields**: `timestamp` (day boundary), `timestamp_grain` (set to "day"), `chain_id`, `market_sector_id`, `business_segment_id`, `to_address`, `transaction_count`

### Component C: Final aggregation and gap filling

- **Purpose**: Finalize daily transaction totals and ensure time-series continuity
- **Logic**: Transaction data is processed directly from the daily aggregation component without additional joining. Currency conversion is not applicable for transaction count metrics. Daily buckets are created using day-boundary timestamp truncation. Schema validation is applied, missing days are filled with zero values to ensure no gaps in the time series, and chain availability filters are used to exclude periods with incomplete data coverage.

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

Confirmed transactions added to the blockchain.

FraxtalFXTL

Transaction count

Transaction count

Competitive landscape

Chain breakdown