← previous blocknext block →recent activity
Analyzing
Block #86,630,308
79 transactions · 56 stateful · 2026-07-09 13:16:09 UTC
Parallelism
76/100
Blocked
77%
Avg conflicts / tx
2.18
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,630,308 · 79 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w19w310w112w414w515w017w120w221w322w430w254w157w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x70ff9262…8d80
0x34b655…2a6f
14 touches
21 conflicts
0x7ce93f3d…b70e
0x34b655…2a6f
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x00f245ce…1e10
0x34b655…2a6f
10 touches
10 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