← previous blocknext block →recent activity

Analyzing

Block #71,172,850

16 transactions · 14 stateful · 2026-04-28 22:44:00 UTC

Parallelism

81/100

Blocked

43%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,172,850  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x148e0217…34a2

0x34b655…2a6f

6 touches
3 conflicts

0x1d731f70…4557

0x34b655…2a6f

6 touches
3 conflicts

0x37379933…2402

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 conflicts

0x5f251b96…6054

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8aa1941d…2988

0x34b655…2a6f

6 touches
3 conflicts

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: 0x34b6552d…112a6f

3 conflicts on slot 0x148e0217dd…f334a2

← previous block·next block →recent activity