← previous blocknext block →recent activity
Analyzing
Block #91,132,885
11 transactions · 9 stateful · 2026-07-28 18:46:27 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,132,885 · 11 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
1w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x609e537a…511d
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xf6366f16…1d91
0x34b655…2a6f
4 touches
1 conflict
0x188b998d…a2fc
0x34b655…2a6f
2 touches
0 conflicts
0x19c5bd01…7daf
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x0ab54c30a6…82b88e
Audit this contract →
← previous block·next block →recent activity