← previous blocknext block →recent activity
Analyzing
Block #86,834,287
26 transactions · 22 stateful · 2026-07-10 12:00:03 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,834,287 · 26 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
1w02w13w17w08w19w210w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb501f5a1…7c96
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xf94d24c1…5f81
0x34b655…2a6f
6 touches
3 conflicts
0xd6b740ec…af37
0x34b655…2a6f
6 touches
3 conflicts
0x00f245ce…1e10
0x34b655…2a6f
6 touches
3 conflicts
0x025fef2f…9738
0x34b655…2a6f
6 touches
3 conflicts
0x0ccbd272…241f
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
3 conflicts on slot 0xb501f5a1f6…187c96
Audit this contract →
← previous block·next block →recent activity