← previous blocknext block →recent activity
Analyzing
Block #86,846,088
18 transactions · 17 stateful · 2026-07-10 13:18:53 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,846,088 · 18 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
1w02w15w07w19w211w212w113w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76c4467d…ce28
0x34b655…2a6f
8 touches
6 conflicts
0x0e5933c1…2063
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x6dd2f894…e40f
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 0x76c4467df9…89ce28
Audit this contract →
← previous block·next block →recent activity