Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Mythos is a specialized gaming blockchain powered by Polkadot Relay chain.

MYTH holders own and govern the protocol.

website

github

twitter

etherscan

Blockchains (L2)

Mythos

# Mythos Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Mythos blockchain over a daily period. This metric provides insight into the network's throughput capacity and actual usage patterns. The calculation takes the total number of unique transactions in a day and divides by the number of seconds in that day (86,400) to determine the average transactions per second.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Mythos blockchain extrinsic records**: Raw transaction data from the Mythos substrate-based blockchain, containing individual extrinsic (transaction) records with timestamps and unique identifiers
- **Chain availability metadata**: Data quality indicators used to filter results and ensure reliable metrics during periods of confirmed chain operation
- **Table partition tracking data**: Internal tracking data used for incremental data processing and ensuring complete coverage

## 3. Step-by-step calculation

### Component A: Transaction facts extraction
- **Purpose**: Extract and standardize raw Mythos transaction data
- **Logic**: Raw extrinsic records from the Mythos blockchain are processed to extract key transaction identifiers and timing information. Each record represents a single transaction (extrinsic) on the Mythos substrate-based chain. The `block_timestamp` field indicates when the transaction was included in a block, and the `extrinsic_id` provides a unique identifier for each transaction. Data is standardized with proper type casting to ensure consistency.
- **Key fields**: `block_timestamp` (transaction inclusion time), `extrinsic_id` (unique transaction identifier), `chain_id` (set to 'mythos')

### Component B: Daily transaction count aggregation
- **Purpose**: Calculate the total number of unique transactions per day
- **Logic**: Transaction records are grouped by day using timestamp truncation to daily boundaries. Within each day, unique transactions are counted using the distinct `extrinsic_id` values to avoid double-counting. This produces a daily transaction count for the Mythos chain. The aggregation includes metadata fields for the product identifier ('Mythos Substrate') and timestamp granularity ('day'). Data validation and gap-filling logic is applied to ensure complete daily coverage, with missing days filled with zero transaction counts.
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (unique daily transaction total), `product_id` ('Mythos Substrate'), `chain_id` ('mythos')

### Final aggregation
- **Combining components**: The daily transaction counts are processed through a transactions per second calculation
- **Currency conversion**: Not applicable for this metric as it measures transaction volume rather than value
- **Time aggregation**: Daily transaction counts are converted to average transactions per second by dividing the daily total by 86,400 (the number of seconds in a day)
- **Final calculation**: The transactions per second value is calculated using safe division of the daily transaction count by the seconds in a day variable. Data validation ensures no gaps in the time series, with missing periods filled with zero values. Chain availability filters are applied to exclude periods where data quality may be compromised, ensuring reliable metric reporting.

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

Average confirmed user transactions added per second.

MythosMYTH

Archived

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown