Zebra perf stats

Updated 2026-10-30T23:10:30Z

Time to accept a new block

Every new Mainnet block goes to all three nodes at once. The numbers are how long each node takes to accept it, over the last 24 hours. Optimized Zebra: zebrad 7.0.0+227.g5527c56, pasta-asm

15.9× faster

Optimized Zebra vs Zebra v7.0.0

Saves 115 ms per block (median of 8 blocks)

1.08× faster

Optimized Zebra vs Zakura

Saves 0.49 ms per block (median of 8 blocks)

Optimized Zebra

6.8 ms

Median of 8 blocks

Latest block 3,536,350: 1.9 ms

Zebra v7.0.0

122.0 ms

Median of 8 blocks

Latest block 3,536,350: 9.3 ms

Zakura

7.5 ms

Median of 8 blocks

Latest block 3,536,350: 1.9 ms

Last 24 hours

The chart needs JavaScript.

Lines are running medians. Shaded: other work on the same machine.
By block size, all time · median ms
SizeBlocksZakuraZebra v7.0.0Optimized ZebraOptimized vs Zebra v7.0.0Optimized vs Zakura
All sizes87.5122.06.815.9× faster1.08× faster
<20 kB32.610.92.34.97× fasterwithin 5% (1.04×)
20–300 kB57.8122.07.118.1× faster1.09× faster
>300 kB0—————
Latest 10 blocks · ms
HeightkBZakuraZebra v7.0.0Optimized Zebra
3,536,3501.6301.99.31.9
3,536,34933.3527.0119.26.6
3,536,3482.3812.610.92.3
3,536,34747.1628.2123.08.4
3,536,34629.1177.8121.97.1
3,536,34513.53116.4169.215.8
3,536,34423.3877.2122.06.1
3,536,34327.1199.5721.18.4

How it works

A Zebra node follows Mainnet and hands each new block to the three nodes with submitblock. The three nodes have no peers and empty mempools, so the time is mostly checking and storing the block. They share one machine with other work. Zakura keeps a pruned chain; both Zebra nodes keep the full chain.