← previous blocknext block →recent activity
Analyzing
Block #86,856,426
23 transactions · 18 stateful · 2026-07-10 14:27:59 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,856,426 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w212w013w116w317w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x793d86d7…acc4
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xe8377f79…5f5e
0x34b655…2a6f
8 touches
6 conflicts
0x288bc578…318e
0x34b655…2a6f
6 touches
3 conflicts
0x30adea6d…8391
0x34b655…2a6f
6 touches
3 conflicts
0x3133f94b…f76b
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
6 touches
3 conflicts
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity