← previous blocknext block →recent activity
Analyzing
Block #86,632,584
53 transactions · 48 stateful · 2026-07-09 13:31:25 UTC
Parallelism
62/100
Blocked
75%
Avg conflicts / tx
3.32
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,632,584 · 53 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w07w18w29w310w411w512w616w235w739w240w841w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4c04ce68…d007
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0x4ec9ff52…e6f7
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity