← previous blocknext block →recent activity
Analyzing
Block #86,757,200
14 transactions · 12 stateful · 2026-07-10 03:24:59 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,757,200 · 14 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
1w02w13w04w15w17w29w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a576152…6d63
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8a471d36…1741
0x34b655…2a6f
4 touches
1 conflict
0x8a471d36…1742
0x34b655…2a6f
4 touches
1 conflict
0xc788862c…c259
0x34b655…2a6f
4 touches
1 conflict
0x440235f2…c9bb
0x34b655…2a6f
4 touches
1 conflict
0x88692611…d222
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 0x5a57615251…046d63
Audit this contract →
← previous block·next block →recent activity