← previous blocknext block →recent activity
Analyzing
Block #86,982,366
27 transactions · 22 stateful · 2026-07-11 04:29:47 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,982,366 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w09w110w211w012w115w016w118w220w321w323w424w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x5bf059d3…c591
0xd32edf…ff58
7 touches
6 conflicts
0x072c4867…c7a9
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x219c6953…c961
0x34b655…2a6f
4 touches
1 conflict
0x3f8b63d0…d24a
0x34b655…2a6f
4 touches
1 conflict
0x448599ef…7518
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity