PulseHawkTestnet and mainnet launch measurement
The first week after a launch shows how a network holds up under real load. We measure that week ourselves and set it against the week before, so your mainnet launch metrics come with a baseline.
What happens in the launch week?
- Before. Our measurement runs from the week before launch and records a baseline.
- Launch. We count through the first week after launch, block by block.
- After. You get a before and after report with charts, the CSV and the method version.
- Publication. Results are published as measured, after you have seen them.
What do we count?
Blocks per second and per minute, the block time distribution, transactions per minute, confirmation time, fees, stale and orphaned blocks and the propagation delay. The full list is in our method.
For a new chain the week before is the last testnet week. For a testnet stress test measurement it is the quiet week before the test.
What does it cost?
Prices as of October 2026, net, plus VAT where it applies. Invoices in euro.
Is it the right fit?
Best for
- Core teams launching a testnet or mainnet
- Foundations that fund a launch and want an outside count
- Teams planning a public testnet stress test
Not for
- Teams that need a code or security review
- A count that has to stay private for good
- Questions about price or market
Questions we get asked
Can you measure our testnet stress test?
Yes. We watch the stress test with our own nodes or header clients and count what reaches the network. The load comes from your test, our part is the count.
How early should we book?
Two weeks before launch is enough for most networks. That leaves time to set up our measurement and record the week before.
What if the launch date moves?
The measurement moves with it. The price stays the same as long as the scope does.