← previous blocknext block →recent activity
Analyzing
Block #91,009,306
16 transactions · 15 stateful · 2026-07-28 08:24:32 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,009,306 · 16 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
2w03w18w29w310w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x442e26a3…e968
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x151b88cc…996c
0x34b655…2a6f
8 touches
6 conflicts
0x47da114c…e383
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
15 conflicts on slot 0x442e26a30f…bbe968
Audit this contract →
← previous block·next block →recent activity