website

twitter

discord

Infrastructure

World Mobile Chain

# World Mobile Chain Transaction count Methodology

## 1. Overview

The WorldMobileChain transaction count metric measures the daily number of unique transactions executed on the WorldMobileChain network, segmented by recipient address (`to_address`). This metric provides insight into network activity and usage patterns by tracking distinct transaction hashes per day and destination address. The calculation uses a simple counting approach that eliminates duplicate transactions and aggregates activity on a daily basis.

## 2. Data sources

The calculation relies on the following raw data sources:

- **WorldMobileChain blockchain transaction records**: Complete transaction data from the WorldMobileChain network including transaction hashes, sender and recipient addresses, timestamps, and gas usage metrics
- **Base chain token metadata**: Token information for the WMTX token since WorldMobileChain uses Base chain infrastructure for token representation (token address `0x3e31966d4f81c72d2a55310a6365a56a4393e98d`)

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Prepares raw WorldMobileChain transaction data for analysis
- **Logic**: Extracts transaction records from WorldMobileChain blockchain data and standardizes field formats. Each transaction record includes essential identifiers like `transaction_hash`, `from_address`, `to_address`, and `block_timestamp`. The component also assigns Base chain token metadata (`WMTX` symbol and contract address) since WorldMobileChain leverages Base chain infrastructure for its token operations. Gas-related metrics including `gas_used`, `l1_gas_used`, `l1_gas_price`, `l1_fee_scalar`, and `gas_price` are preserved for potential downstream analysis.
- **Key fields**: `block_timestamp` for temporal analysis, `transaction_hash` for unique transaction identification, `to_address` for recipient-based segmentation, gas metrics for network cost analysis

### Component B: Daily transaction aggregation
- **Purpose**: Aggregates transaction activity on a daily basis with recipient-level granularity
- **Logic**: Groups transaction data by day boundaries using timestamp truncation on `block_timestamp`. For each day and `to_address` combination, counts the number of distinct `transaction_hash` values to eliminate any potential duplicates. Assigns standard dimensional attributes including `worldmobilechain` as the `chain_id`, `day` as the `timestamp_grain`, and null values for `product_id` and `contract_name` since these dimensions are not applicable to this blockchain-level metric. For incremental processing, filters to include only recent days based on the configured lookback period to optimize performance.
- **Key fields**: `timestamp` truncated to day boundaries, `transaction_count` representing distinct transaction hash counts, `to_address` for recipient-based segmentation

### Final aggregation
- **Combining components**: The daily aggregation results flow directly into the finalization process without additional joining or combination steps
- **Currency conversion**: Not applicable - this is a count-based metric that does not involve monetary values
- **Time aggregation**: Daily boundaries are established by truncating `block_timestamp` to the day level, ensuring consistent 24-hour measurement periods
- **Final calculation**: The final metric value represents the count of distinct transaction hashes per day per recipient address. A finalization macro validates the data structure, ensures no gaps exist in the time series by applying a fill-zeros strategy for missing days, and applies chain availability filtering to include only data from operational time periods

## Critical notes

- **Chain infrastructure**: WorldMobileChain uses Base chain infrastructure for token operations, which is why Base chain token metadata is referenced in the transaction processing
- **Recipient-level granularity**: The metric provides transaction counts segmented by `to_address`, enabling analysis of activity patterns across different destination addresses
- **Duplicate handling**: The use of `count(distinct transaction_hash)` ensures that any duplicate transaction records are eliminated from the final count
- **Gap filling**: Missing days in the time series are automatically filled with zero values to maintain complete daily coverage for reporting and analysis purposes

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

Confirmed transactions added to the blockchain.

World Mobile ChainWMTX

Transaction count

Transaction count

Competitive landscape

Chain breakdown