← previous blocknext block →recent activity
Analyzing
Block #86,916,436
18 transactions · 15 stateful · 2026-07-10 21:09:16 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,916,436 · 18 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
6w07w19w210w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xf0feb15e…420b
0x34b655…2a6f
6 touches
3 conflicts
0x875c3459…2878
0x34b655…2a6f
6 touches
3 conflicts
0x875c3459…2879
0x34b655…2a6f
6 touches
3 conflicts
0xb338f13e…1372
0x34b655…2a6f
6 touches
3 conflicts
0xa1f4bc22…c630
0x34b655…2a6f
4 touches
2 conflicts
0x3d22c439…de6d
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity