PulseHawkIndependent TPS verification, claimed vs measured
A TPS claim is a number from a test. We verify the TPS claim against what the network does in our own measurement, inside a dated window, and set real TPS vs claimed TPS side by side with the raw data.
How does a TPS verification work?
- The claim. You send the TPS number and where it was published, a paper, a dashboard or a post.
- The conditions. We write down what stands behind the claim, transaction type and size, number of nodes, network and date.
- The measurement. We count ourselves, with our own node or header client, over an agreed window in UTC. Transactions per minute, blocks per second and confirmation time.
- The note. You get a dated note with claimed and measured numbers next to each other, plus the CSV.
What does it cost?
Prices as of October 2026, net, plus VAT where it applies. Invoices in euro.
Longer windows or a measured testnet stress test are custom scope, on request.
Is it the right fit?
Best for
- Teams that want to check their own TPS number before they publish it
- Foundations and grant committees that need a neutral view of a claim
- Exchanges and integrators that plan capacity
Not for
- Teams that need their code reviewed
- Anyone who needs a number before the network runs
- Questions about price or market
Questions we get asked
Why is measured TPS usually lower than claimed TPS?
A claim often comes from a lab test with simple transfers on a few nodes close together. A public network carries mixed transactions over real distances. Both numbers can be honest, they just describe different conditions. We show both and name the conditions.
Can you verify a TPS claim on a network that is new to you?
Yes. We set up our own node or header client for the job. The setup time is part of the agreed window.
Will the result be published?
Yes. Results are published as measured. You see them before publication and can correct facts, not findings.