← previous blocknext block →recent activity
Analyzing
Block #91,086,366
18 transactions · 18 stateful · 2026-07-28 14:52:25 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,086,366 · 18 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
1w05w16w07w18w09w115w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f6df54…4259
0x7b9256…1fb2
4 touches
1 conflict
0x145b9bbf…e50e
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50f
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x901f4dfc…1ba4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9e04a514…7824
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: 0x7b9256fd…e21fb2
1 conflict on slot 0x64f6df540a…da4259
Audit this contract →
← previous block·next block →recent activity