← previous blocknext block →recent activity
Analyzing
Block #86,701,838
25 transactions · 20 stateful · 2026-07-09 21:15:02 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,701,838 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w17w08w19w210w311w212w415w516w118w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
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 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity