← previous blocknext block →recent activity
Analyzing
Block #86,851,304
68 transactions · 50 stateful · 2026-07-10 13:53:43 UTC
Parallelism
74/100
Blocked
68%
Avg conflicts / tx
1.84
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,851,304 · 68 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w18w010w114w115w216w318w021w122w223w331w136w237w342w848w1150w351w152w454w455w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xbcdee322…f454
0xa6afd3…d132
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0x3413a430…234a
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x006ee1d9…5485
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…00c9
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity