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

Injective is a smart contract platform for decentralized finance applications (a blockchain) and an orderbook exchange protocol. Injective was founded by Eric Chen, Albert Chon etc. and launched in 2020. Note that this dashboard only tracks Injective's blockchain business.

INJ holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue) via Burn Auctions. Injective's investors include Binance, Jump Crypto, Mark Cuban, etc.

github

twitter

discord

website

Blockchains (L1)

Injective

# Injective Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Injective protocol over a daily period. This metric provides insight into network throughput and activity levels across both Injective's EVM-compatible layer and its native Cosmos SDK chain. The calculation aggregates transaction counts from both networks and divides by the number of seconds in a day (86,400) to produce a daily average TPS value.

## 2. Data sources

The calculation uses transaction data from two distinct blockchain networks within the Injective ecosystem:

- **Injective EVM transaction records**: Complete transaction data from Injective's Ethereum-compatible layer, including transaction hashes, block timestamps, sender/receiver addresses, gas usage, and effective gas prices
- **Injective EVM block data**: Block-level information containing base fee per gas data for EIP-1559 transaction fee calculations
- **Injective Cosmos transaction records**: Native Cosmos SDK transaction data from Injective's base layer, including block timestamps, transaction hashes, and transaction fee information with currency denominations

## 3. Step-by-step calculation

### Component A: Injective EVM transaction processing
- **Purpose**: Extract and process all transactions from Injective's EVM-compatible layer
- **Logic**: Raw transaction data is filtered and cleaned, with safe casting applied to handle data quality issues. Block timestamps are used to establish transaction timing, and transaction hashes serve as unique identifiers. The component joins transaction data with block information to enrich records with base fee data needed for gas fee calculations. Key addresses (`from_address`, `to_address`) are preserved along with gas usage metrics (`gas_used`, `effective_gas_price`)
- **Key fields**: `block_timestamp` for daily aggregation boundaries, `transaction_hash` for unique counting, `from_address` and `to_address` for transaction flow analysis, `gas_used` and `effective_gas_price` for fee calculations, and `base_fee_per_gas` from block data

### Component B: Injective cosmos transaction processing  
- **Purpose**: Extract and process all transactions from Injective's native Cosmos SDK chain
- **Logic**: Cosmos transaction data is processed with regex pattern matching to parse transaction fee strings, separating numeric amounts from currency units. The fee parsing uses regex to extract digits and alphabetic currency codes from combined fee strings. Block timestamps establish transaction timing for daily aggregation
- **Key fields**: `block_timestamp` for temporal boundaries, `transaction_hash` for unique identification, `transaction_fee` parsed into numeric amounts and currency `unit` strings

### Component C: Transaction count aggregation
- **Purpose**: Combine and count transactions from both Injective networks by day
- **Logic**: Both EVM and Cosmos transaction datasets are aggregated separately by truncating timestamps to daily boundaries and counting distinct transaction hashes. Each chain maintains separate product identifiers (`Injective EVM` and `Injective Cosmos`) and chain IDs for tracking. The data is classified under the `blockchains_l1` market sector and `blockchain` business segment. EVM transactions preserve `to_address` information while Cosmos transactions set this as null due to different addressing models. The two aggregated datasets are then combined using a union operation
- **Key fields**: `timestamp` truncated to daily boundaries, `transaction_count` as distinct hash counts, `product_id` and `chain_id` for network identification

### Final aggregation
- **Combining components**: The combined transaction counts from both networks are processed through data quality validation and gap-filling procedures to ensure completeness across the date range
- **Time aggregation**: All calculations use daily boundaries established by truncating block timestamps to day precision, ensuring consistent 24-hour periods for TPS calculations  
- **Final calculation**: The transactions per second value is computed by dividing the daily transaction count by 86,400 (the number of seconds in a day), providing an average TPS rate for each day. Chain availability filters are applied to exclude periods where data may be incomplete or unreliable

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

Average confirmed user transactions added per second.

InjectiveINJ

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown