← previous blocknext block →recent activity
Analyzing
Block #86,700,844
25 transactions · 23 stateful · 2026-07-09 21:08:24 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,700,844 · 25 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
4w09w010w111w212w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x4e5b8dd6…a766
0x34b655…2a6f
6 touches
3 conflicts
0x4740ce34…74c6
0x34b655…2a6f
6 touches
3 conflicts
0xae901867…8085
0x34b655…2a6f
6 touches
3 conflicts
0xae901867…8086
0x34b655…2a6f
6 touches
3 conflicts
0x4cf39eee…2213
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity