← previous blocknext block →recent activity
Analyzing
Block #86,753,861
20 transactions · 18 stateful · 2026-07-10 03:02:40 UTC
Parallelism
80/100
Blocked
28%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,753,861 · 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
5w06w17w19w210w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6016de75…62e1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6016de75…62e0
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x94cd6ce2…7b45
0x34b655…2a6f
5 touches
3 conflicts
0x8f2a8a62…19a7
0x34b655…2a6f
5 touches
3 conflicts
0x58c5d187…303b
0x34b655…2a6f
4 touches
1 conflict
0x58c5d187…303c
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 0x6016de752c…f462e1
Audit this contract →
← previous block·next block →recent activity