← previous blocknext block →recent activity

Analyzing

Block #72,571,152

9 transactions · 6 stateful · 2026-05-05 10:06:59 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,571,152  ·  9 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

0x6549da7a…6602

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbe1d876b…bde4

0x065c9d…c394

5 touches
3 conflicts

0xe5bdffa1…140b

0x065c9d…c394

5 touches
3 conflicts

0x69f864cf…d619

0x065c9d…c394

3 touches
1 conflict

0x5e957b7d…86d1

0x065c9d…c394

2 touches
0 conflicts

0x78cf3734…6917

0x065c9d…c394

2 touches
0 conflicts

0xb548d652…05e1

0x065c9d…c394

2 touches
0 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: 0x065c9d28…a9c394

3 conflicts on slot 0x6549da7ae4…f96602

← previous block·next block →recent activity