← previous blocknext block →recent activity

Analyzing

Block #72,571,109

7 transactions · 6 stateful · 2026-05-05 10:06:42 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x08fdbdc9…aa7c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x1cfa11ca…f1c4

0x065c9d…c394

5 touches
3 conflicts

0x11f195f1…95eb

0x065c9d…c394

4 touches
1 conflict

0x7d00decc…4043

0x065c9d…c394

4 touches
1 conflict

0xdd1124fd…7612

0x065c9d…c394

3 touches
1 conflict

0x354f216a…c210

0x065c9d…c394

3 touches
1 conflict

0xc926c354…6032

0x065c9d…c394

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

3 conflicts on slot 0x08fdbdc9d6…d9aa7c

← previous block·next block →recent activity