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

Flow is a smart contract platform for decentralized applications (a blockchain). Flow was founded by Roham Gharegozlou, Dieter Shirley and Mikhael Naayem and launched in 2019.

FLOW holders own and govern the protocol. They currently don’t take a cut of the total transaction fees paid by users (revenue). Flow’s investors include a16z, Coatue, Coinfund, Fabric Ventures, etc.

governance

github

twitter

discord

website

Blockchains (L1)

Flow

# Flow Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average rate of transaction processing on the Flow blockchain over a day. This metric combines transaction activity from both Flow execution environments: Flow EVM (EVM-compatible transactions) and Flow (native Flow/Cadence transactions). The calculation divides the total daily transaction count by 86,400 seconds to provide a standardized throughput metric for comparing Flow's transaction processing capacity.

## 2. Data sources

- **Flow EVM transaction records**: Complete transaction data from Flow's EVM-compatible execution environment, including transaction hashes, block timestamps, addresses, and gas information
- **Flow transaction records**: Complete transaction data from Flow's native Cadence execution environment, including transaction hashes, block timestamps, payer information, and fee data

## 3. Step-by-step calculation

### Component A: Flow EVM transaction aggregation
- **Purpose**: Count daily Flow EVM transactions
- **Logic**: Extract Flow EVM transaction records and group by day, counting distinct `transaction_hash` values to avoid duplicates. Each transaction includes `block_timestamp`, `from_address`, `to_address`, `gas_used`, and `gas_price` information. The data is truncated to day-level timestamps for aggregation.
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_hash` for unique transaction identification, address fields for transaction routing

### Component B: Flow transaction aggregation  
- **Purpose**: Count daily Flow transactions
- **Logic**: Extract Flow transaction records and group by day, counting distinct `transaction_hash` values. Each transaction includes `block_timestamp`, `payer`, `gas_limit`, and `fee_amount` information. The data is truncated to day-level timestamps for aggregation.
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_hash` for unique transaction identification, `payer` for transaction originator

### Component C: Transaction count combination
- **Purpose**: Combine both transaction types into unified daily counts
- **Logic**: Union the Flow EVM and Flow daily transaction counts to create a comprehensive view of all Flow blockchain activity. Both transaction types are classified with appropriate product identifiers (Flow EVM as `Flow EVM`, Flow as `Flow`) and chain identifiers.
- **Key fields**: Combined `transaction_count` values, `product_id` for distinguishing transaction types, `chain_id` for blockchain identification

### Final aggregation
- **Combining components**: The combined transaction counts from both execution environments are summed by day to get total daily transaction volume across the entire Flow blockchain
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily aggregation with day-level timestamp truncation
- **Final calculation**: Divide the total daily transaction count by 86,400 seconds (the number of seconds in a day) to calculate the average transactions per second for each day. Missing data periods are filled with zeros to maintain continuity in the time series.

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

Average confirmed user transactions added per second.

FlowFLOW

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown