Users and developers interact with the protocol by writing and deploying confidential smart contracts using Midnight's Compact language and sending private transactions with zero-knowledge proofs.

Midnight is a privacy-first Layer 1 blockchain that blends public verifiability with confidential data handling. It uses zero-knowledge proofs (ZK-SNARKs) and selective disclosure to enable applications that verify correctness without revealing sensitive data. Midnight operates as a partner chain to Cardano and is designed for building confidential smart contracts using its Compact language and the Kachina protocol.

Midnight is developed by Input Output Global (IOG), the company behind Cardano.

website

twitter

Blockchains (L1)

Midnight

# midnight Transactions per second Methodology

## 1. Overview

Transactions per second measures the average number of confirmed transactions added to the midnight blockchain each second. Network throughput and real-time usage are reflected by this metric. All transactions, including both user and system operations, are included in the calculation to match cross-chain conventions. This metric is utilized to evaluate the scalability and active adoption of the midnight network over time.

## 2. Data sources

- **Blockchain events**: Block and transaction records extracted from the midnight ledger, covering the midnight chain

## 3. Step-by-step calculation

### Component A: Block and transaction deduplication

- **Purpose**: Ensure only unique blocks and transactions from the latest ledger state are processed
- **Logic**: Block and transaction records are filtered to the latest export partition. Duplicate records generated by non-idempotent loading processes are removed by retaining only the most recently inserted record for each unique block and transaction identifier. Block timestamps are converted from epoch milliseconds to standard timestamp format.
- **Key fields**: `block_timestamp`, `block_id`, `transaction_id`

### Component B: Transaction enrichment

- **Purpose**: Associate transactions with block times
- **Logic**: Transactions are joined with their corresponding blocks using the block identifier to inherit block timestamps.
- **Key fields**: `block_id`, `block_timestamp`

### Component C: Daily transaction aggregation

- **Purpose**: Aggregate transactions into daily totals
- **Logic**: The deduplicated transactions are aggregated by truncating block timestamps to daily boundaries. The total number of unique transaction identifiers is counted for each day.
- **Key fields**: `block_timestamp`, `transaction_id`

### Component D: Transactions per second calculation

- **Purpose**: Calculate the average throughput per second
- **Logic**: The daily transaction count is divided by the total number of seconds in a day (86,400) to determine the average transactions per second. The resulting values are finalized to ensure continuous daily coverage.
- **Key fields**: `transaction_count`, `transactions_per_second`

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

Average confirmed user transactions added per second.

MidnightNIGHT

Maintenance

Transactions per second

Transactions per second

Competitive landscape