← previous blocknext block →recent activity
Analyzing
Block #72,221,901
18 transactions · 13 stateful · 2026-05-03 19:16:26 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,221,901 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w114w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc53af6f0…50bd
0x34b655…2a6f
6 touches
3 conflicts
0x257251ca…49b8
0x34b655…2a6f
6 touches
3 conflicts
0x9dc9fa5f…7f23
0x34b655…2a6f
6 touches
3 conflicts
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x220f4f84…15f8
0x34b655…2a6f
4 touches
1 conflict
0x77905798…fe3d
0x34b655…2a6f
4 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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity