Block #72,394,870

← previous blocknext block →recent activity

Analyzing

Block #72,394,870

9 transactions · 7 stateful · 2026-05-04 14:33:01 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2b42047a…c15c

0x065c9d…c394

4 touches
1 conflict

0x135c6ba8…6499

0x065c9d…c394

3 touches
1 conflict

0x92770cb2…1a8c

0x065c9d…c394

3 touches
1 conflict

0xce8abcd4…e668

0x065c9d…c394

3 touches
1 conflict

0x48c6e5aa…cc95

0x065c9d…c394

3 touches
1 conflict

0xba948623…896e

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

1 conflict on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity