Transaction Count (24h)

Every confirmed transaction is recorded in a block, so the count is directly observable from chain data with no estimation. It is the most basic activity measure a blockchain produces and underlies throughput and average fee calculations. Its weakness is not accuracy but comparability.

How it is computed

count of transactions included in blocks confirmed over the trailing 24 hours

Where it misleads

A transaction is not a comparable unit between chains: a single Bitcoin transaction can pay hundreds of recipients from many inputs, an account-based chain needs one transaction per payment, and a layer 2 compresses thousands of user operations into one settlement transaction on its parent chain. Some high-throughput networks have historically included consensus vote messages in the raw count, which can dwarf genuine user activity and make cross-chain rankings meaningless. Inscription waves and spam are cheap on low-fee chains and can multiply the count without a corresponding change in economic activity. Providers differ on whether internal contract calls and failed transactions are counted.

Reading a high or a low value

A higher count means more transactions were confirmed that day on that chain. Comparisons are meaningful within one chain over time and unreliable between chains with different transaction models.