← previous blocknext block →recent activity
Analyzing
Block #86,820,857
14 transactions · 11 stateful · 2026-07-10 10:30:09 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,820,857 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa962a6d7…b211
0x34b655…2a6f
6 touches
3 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x194be77e…58ae
0x34b655…2a6f
4 touches
1 conflict
0x22af2208…099e
0x34b655…2a6f
4 touches
1 conflict
0x2a81695b…2e8c
0x34b655…2a6f
4 touches
1 conflict
0x38b61269…48d7
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 0xa962a6d7cd…9fb211
Audit this contract →
← previous block·next block →recent activity