Block #72,571,394

← previous blocknext block →recent activity

Analyzing

Block #72,571,394

7 transactions · 6 stateful · 2026-05-05 10:08:35 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,571,394  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6d6f76dd…de6c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xae00c5a3…e562

0x065c9d…c394

3 touches
1 conflict

0xbbaef107…88af

0x065c9d…c394

3 touches
1 conflict

0x2fe2b516…a80b

0x065c9d…c394

2 touches
0 conflicts

0x3f2018d5…d8f1

0x065c9d…c394

2 touches
0 conflicts

0x5b9da72e…4206

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

1 conflict on slot 0x6d6f76dd1d…1bde6c

← previous block·next block →recent activity