← previous blocknext block →recent activity
Analyzing
Block #86,851,171
44 transactions · 35 stateful · 2026-07-10 13:52:50 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
2.52
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,851,171 · 44 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w29w315w016w117w218w319w420w521w622w723w824w925w1030w1132w133w335w436w539w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x8d888c90…5479
0x34b655…2a6f
10 touches
10 conflicts
0x428b6e5b…8909
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x371143a8…fdb0
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x62db95d4…351c
0x34b655…2a6f
8 touches
6 conflicts
0x63b15849…80b2
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity