← previous blocknext block →recent activity
Analyzing
Block #72,495,668
22 transactions · 20 stateful · 2026-05-05 01:44:26 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,495,668 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w09w110w211w312w313w316w417w518w520w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
10 touches
10 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x9666ffc6…30d2
0xd32edf…ff58
7 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
6 touches
3 conflicts
0x031d16b4…895a
0x34b655…2a6f
6 touches
3 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: Perpl
10 conflicts on slot 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity