← previous blocknext block →recent activity
Analyzing
Block #86,880,869
31 transactions · 23 stateful · 2026-07-10 17:11:34 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,880,869 · 31 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
1w03w16w07w18w29w310w411w514w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x1951ee47…540f
0x34b655…2a6f
8 touches
6 conflicts
0x288bc578…318e
0x34b655…2a6f
8 touches
6 conflicts
0x321eac33…6aca
0x34b655…2a6f
8 touches
6 conflicts
0x41a19c97…4d3f
0x34b655…2a6f
8 touches
6 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x9ad66bbf…929c
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity