← previous blocknext block →recent activity
Analyzing
Block #86,668,729
40 transactions · 35 stateful · 2026-07-09 17:34:03 UTC
Parallelism
75/100
Blocked
71%
Avg conflicts / tx
1.93
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,668,729 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w18w09w111w012w113w214w315w416w517w618w719w821w223w624w127w128w229w130w231w332w435w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x98d58911…19f2
0x34b655…2a6f
8 touches
6 conflicts
0xa29182a1…c12c
0x34b655…2a6f
8 touches
6 conflicts
0xb25fa8e2…c9ef
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity