← previous blocknext block →recent activity
Analyzing
Block #86,823,617
16 transactions · 16 stateful · 2026-07-10 10:48:43 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,823,617 · 16 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
1w02w13w28w09w110w311w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5523e84b…0ce4
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf871d18f…979a
0x34b655…2a6f
6 touches
3 conflicts
0x03cf8a66…08c6
0x34b655…2a6f
4 touches
1 conflict
0x215fc0bb…53b3
0x34b655…2a6f
4 touches
1 conflict
0x7545cfb2…cd6f
0x34b655…2a6f
4 touches
1 conflict
0x86f32276…0ebf
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
6 conflicts on slot 0x5523e84b06…960ce4
Audit this contract →
← previous block·next block →recent activity