Block #72,394,823

← previous blocknext block →recent activity

Analyzing

Block #72,394,823

9 transactions · 9 stateful · 2026-05-04 14:32:42 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,394,823  ·  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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xdd91bb1e…8300

0x065c9d…c394

3 touches
1 conflict

0x38b373f7…3109

0x065c9d…c394

2 touches
0 conflicts

0x7325acfa…bba2

0x065c9d…c394

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity