← previous blocknext block →recent activity
Analyzing
Block #86,945,685
18 transactions · 17 stateful · 2026-07-11 00:24:43 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,945,685 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w26w08w39w110w011w212w315w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e303d0b…01bb
0x34b655…2a6f
10 touches
10 conflicts
0x757c98b7…6a2a
0xd32edf…ff58
7 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xef5838dd…00a4
0x34b655…2a6f
6 touches
3 conflicts
0x16363afe…d410
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4722
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4723
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x6e303d0b67…b801bb
Audit this contract →
← previous block·next block →recent activity