← previous blocknext block →recent activity
Analyzing
Block #86,608,868
42 transactions · 36 stateful · 2026-07-09 10:53:01 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
2.17
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,608,868 · 42 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
1w02w13w04w06w17w110w211w012w113w214w315w416w517w618w719w820w924w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
10 touches
10 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
10 touches
10 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
10 touches
10 conflicts
0x2c464079…5988
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity