Five GKE blasters, each in the same cloud zone as the validator it hammers, fired native transfers as fast as the chain would take them. Throughput here is measured from execution results - transactions actually included in blocks - not from what we managed to submit.
Highest sustained throughput each network has been recorded producing. Telcoin's bar is what we demonstrated in this short flood - injection-limited, not the chain's ceiling.
Telcoin devnet: measured peak this run. Others: max recorded TPS (chainspect.app, Aug 2026).
Transactions included per second across the run. TN produces several blocks per second under load, so each second sums every block it stamped.
Bucketed from the on-chain block series. The dashed line marks single-block capacity (1,428 tx).
Each block holds 1,428 native transfers (30M gas / 21k). Under the flood the chain filled entire blocks - and stacked several full blocks into a single second.
Busiest block vs block capacity.
Throughput claims are easy to inflate by counting submissions. Every figure here comes from blocks the chain actually produced.
Hundreds of accounts, each pinned to one node so its nonce sequence stays intact in that node's mempool - no gaps to stall block building.
EIP-1559 transfers signed locally with managed nonces, fired via raw submission. The client never waits on the chain to build the next tx.
We scan every block produced during the run and count included transactions - realized TPS, bucketed per timestamp-second.
Five blasters, one chain. Submissions sum; landed throughput is taken over the union of blocks so the shared chain is counted once.
The validators are spread across five regions on four continents, so "in-zone" meant a small GKE cluster in each - the blaster reaches its node in well under a millisecond.
| Network | Peak / max TPS | Theoretical | Family |
|---|