← previous blocknext block →recent activity
Analyzing
Block #86,623,320
67 transactions · 51 stateful · 2026-07-09 12:29:30 UTC
Parallelism
69/100
Blocked
78%
Avg conflicts / tx
3.7
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #86,623,320 · 67 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w210w113w214w315w416w517w518w656w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
38 touches
171 conflicts
0x3230277c…ef39
0xc8689a…ee79
24 touches
66 conflicts
0x076fc848…5c81
0x34b655…2a6f
24 touches
66 conflicts
0xda46a376…f6a6
0x34b655…2a6f
24 touches
66 conflicts
0x89999c15…fdac
0x34b655…2a6f
24 touches
66 conflicts
0xcd81cc7b…8da0
0x34b655…2a6f
24 touches
66 conflicts
0x2c2761c0…476e
0x34b655…2a6f
24 touches
66 conflicts
0x30ae635d…5e67
0x34b655…2a6f
24 touches
66 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
171 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity