← previous blocknext block →recent activity
Analyzing
Block #86,633,722
40 transactions · 31 stateful · 2026-07-09 13:39:01 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
1.68
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,633,722 · 40 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w211w012w113w214w315w416w517w618w719w820w221w222w135w1036w1137w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
12 touches
15 conflicts
0x4572c9a0…5cf9
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x727fbce7…0c80
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
12 touches
15 conflicts
0xc1647db7…f853
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity