News5 min readJun 2, 2026

BlockDAG Testnet Update: New Throughput Numbers Are In

The latest testnet results show significant improvements in transaction throughput.

DA

@dagwatcher

On-chain analyst and long-term BDAG holder. Tracking the network since genesis.

The numbers

The BlockDAG core team published testnet performance results this week, and they're worth paying attention to. Under sustained load testing, the network achieved a peak of 12.4 blocks per second with an average transaction confirmation time of 2.1 seconds. At standard transaction sizes, that translates to roughly 8,000 transactions per second — a significant jump from the 6,200 TPS recorded in the previous testnet cycle.

What changed

The improvement comes primarily from two optimizations: a revised block propagation protocol that reduces the time between block creation and network-wide acknowledgment, and an updated DAG ordering algorithm that processes the graph topology more efficiently under high block rates.

The propagation changes are particularly interesting. The previous protocol had a known bottleneck when more than 8 blocks per second were being produced simultaneously — nodes would occasionally fall behind in processing incoming blocks, creating temporary forks that had to be resolved. The new protocol handles up to 15 blocks per second before showing similar degradation.

Context and caveats

Testnet performance doesn't always translate directly to mainnet. Testnet nodes are typically run by technically sophisticated operators on well-provisioned hardware, and the network topology is more controlled than a decentralized mainnet. Real-world performance will depend heavily on the geographic distribution of nodes and the hardware profile of the average validator.

That said, the direction is clearly positive. Each testnet cycle has shown measurable improvement, and the core team has been transparent about the methodology.

What to watch next

The team has indicated that the next testnet phase will focus on stress-testing the network under adversarial conditions — specifically, simulating high rates of conflicting transactions to validate the double-spend prevention mechanisms at scale. That's the test that really matters for mainnet readiness.

@dagwatcher·TestnetThroughputDevelopmentNews

Stay Ahead of the DAG.

Weekly BlockDAG analysis, news, and tutorials — straight to your inbox.