← previous blocknext block →recent activity
Analyzing
Block #86,911,015
24 transactions · 18 stateful · 2026-07-10 20:33:05 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,911,015 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w111w212w315w016w417w522w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408fa1ce…dddc
0x34b655…2a6f
8 touches
6 conflicts
0x5d7f309d…5145
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0x6b2ba712…0214
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xa7e45018…b59c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x408fa1cec1…bfdddc
Audit this contract →
← previous block·next block →recent activity