website

twitter

Blockchains (L2)

Humanity Protocol

# Humanity Protocol Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the Humanity blockchain per second on a daily basis. This metric provides insight into the network's throughput and activity levels by converting daily transaction volumes into a standardized per-second rate. The calculation divides the total number of unique transactions in a day by the number of seconds in that day (86,400).

## 2. Data sources

The calculation uses the following data sources:
- **Humanity blockchain transaction records**: Raw transaction data from the Humanity blockchain containing transaction hashes, block timestamps, sender addresses (`from_address`), recipient addresses (`to_address`), and associated metadata
- **Chain availability configuration**: Internal configuration data used to validate chain availability and apply data quality filters

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw transaction records from the Humanity blockchain
- **Logic**: Raw transaction data is retrieved from Humanity blockchain records and standardized by casting fields to appropriate data types. The `block_timestamp` field is converted to a timestamp format, while `transaction_hash`, `from_address`, and `to_address` are converted to string format. A static chain identifier 'humanity' is assigned to all records.
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `transaction_hash` (unique transaction identifier), `from_address` and `to_address` (sender and recipient addresses), and `chain` (blockchain identifier)

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions per day and organize by relevant dimensions
- **Logic**: Transaction records are grouped by day using timestamp truncation to daily boundaries. For each day, the system counts distinct transaction hashes to avoid double-counting any transactions. The aggregation includes dimensional attributes such as chain identifier ('humanity'), market sector ('blockchains_l2'), and business segment ('blockchain'). Incremental processing ensures only recent data is reprocessed during updates.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (set to 'day'), `chain_id`, `market_sector_id`, `business_segment_id`, and `transaction_count` (distinct count of transaction hashes)

### Component C: Transactions per second calculation
- **Purpose**: Convert daily transaction counts into per-second rates
- **Logic**: Daily transaction counts are divided by the number of seconds in a day using a safe division operation to handle any edge cases. The system uses a predefined variable for seconds in a day (86,400) to ensure consistency. Data is grouped by timestamp, timestamp grain, product ID, and chain ID to maintain proper dimensional structure.
- **Key fields**: `timestamp`, `timestamp_grain`, `product_id`, `chain_id`, and `transactions_per_second` (calculated rate)

### Final aggregation
- **Combining components**: The daily transaction counts from component B flow directly into component C for per-second rate calculation
- **Currency conversion**: Not applicable for this metric as it measures transaction volume, not monetary value  
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation, with each day's total transactions divided by 86,400 seconds
- **Final calculation**: The transactions per second rate equals the total unique transactions in a day divided by 86,400 seconds, providing an average TPS for that day. Data quality validations and gap-filling with zeros ensure complete time series coverage.

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

Average confirmed user transactions added per second.

Humanity ProtocolH

Transactions per second

Transactions per second

Competitive landscape