← previous blocknext block →recent activity
Analyzing
Block #86,659,396
20 transactions · 16 stateful · 2026-07-09 16:31:49 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,659,396 · 20 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
6w07w18w29w211w012w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16784c1e…043f
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0xe8a876d4…921a
0xb1dbf0…c0d3
4 touches
1 conflict
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x1837cfc2…7957
0x34b655…2a6f
4 touches
1 conflict
0x3522af60…d679
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0xb5b586a1…51cb
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
3 conflicts on slot 0x16784c1e18…8a043f
Audit this contract →
← previous block·next block →recent activity