twitter

discord

website

Blockchains (L1)

Movement

# Movement Active users (daily) Methodology

## 1. Overview

Movement metrics user DAU measures the daily active users on the Movement blockchain by counting unique transaction senders per day. This metric answers the business question "How many distinct users are transacting on Movement each day?" The calculation approach identifies unique sender addresses from all successful transactions within each daily time period, providing a count of active participants in the Movement ecosystem.

## 2. Data sources

- **Movement blockchain transaction records**: Raw transaction data from the Movement blockchain containing transaction metadata, sender addresses, timestamps, and gas information
- **Genesis transaction data**: Special handling for Movement blockchain genesis transactions that require timestamp normalization

## 3. Step-by-step calculation

### Component A: Transaction data processing
- **Purpose**: Extract and normalize raw Movement blockchain transaction data
- **Logic**: The system retrieves all transaction records from Movement blockchain data, including fields like block timestamp, transaction hash, sender address, gas used, and gas unit price. Gas unit prices are converted from raw blockchain units to normalized values by dividing by 10^8. Special logic handles genesis transactions by normalizing any transactions with timestamps before January 1, 2000 to a fixed date of December 5, 2024. Regular transactions must have timestamps after January 1, 2000 to be included. All processed transactions are combined into a unified dataset.
- **Key fields**: `block_timestamp` (transaction timing), `hash` (transaction identifier), `sender` (user address), `gas_used` (gas consumed), `gas_unit_price` (normalized gas price)

### Component B: Daily user identification
- **Purpose**: Identify unique daily active users from transaction senders
- **Logic**: Block timestamps are truncated to daily boundaries to group transactions by date. The system then extracts distinct sender addresses for each day, treating each unique sender as a daily active user. Incremental processing logic ensures only data from recent partitions (based on maximum partition date minus configurable lookback days) is processed to optimize performance. Each unique sender per day becomes one record in the DAU calculation.
- **Key fields**: `timestamp` (daily boundary), `sender` (converted to `user_dau` field), `timestamp_grain` (set to 'day')

### Final aggregation
- **Combining components**: The transaction data processing feeds directly into the daily user identification component, with no separate joining required since both operations work on the same transaction dataset
- **Currency conversion**: No currency conversion is needed as this metric counts users rather than monetary values
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to the day level, ensuring each user is counted once per calendar day regardless of how many transactions they sent
- **Final calculation**: The metric value for each day equals the count of distinct sender addresses that initiated at least one transaction on that day, with additional metadata fields added for categorization including chain identifier ('movement'), user type ('Transaction sender'), market sector ('blockchains_l2'), business segment ('blockchain'), and null product identifier

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

Unique revenue-generating users over a fixed 24-hour window.

MovementMOVE

Archived

Active users (daily)

Active users (daily)

Competitive landscape