← previous blocknext block →recent activity
Analyzing
Block #86,798,752
23 transactions · 16 stateful · 2026-07-10 08:02:20 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,798,752 · 23 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
6w07w18w210w311w412w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd81afb3…de3d
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfb0a4eb5…8be3
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09c
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09d
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
10 conflicts on slot 0xdd81afb388…c1de3d
Audit this contract →
← previous block·next block →recent activity