← previous blocknext block →recent activity

Analyzing

Block #99,953,205

21 transactions · 20 stateful · 2026-08-28 17:04:40 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,953,205  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x9ed5aa7d…9481

0x34b655…2a6f

8 touches
6 conflicts

0x932a9590…0b19

0x34b655…2a6f

8 touches
6 conflicts

0x53f7214d…8ec6

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x53ca1284…cb2c

0x34b655…2a6f

6 touches
3 conflicts

0x3b59f067…333f

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

6 conflicts on slot 0x9ed5aa7d72…cc9481

← previous block·next block →recent activity