← previous blocknext block →recent activity
Analyzing
Block #86,632,524
52 transactions · 44 stateful · 2026-07-09 13:31:00 UTC
Parallelism
65/100
Blocked
68%
Avg conflicts / tx
3.1
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,632,524 · 52 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
1w02w13w04w15w16w07w110w211w313w216w017w118w219w320w421w522w623w741w143w444w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0xa29182a1…c12c
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x3a37aad1…720f
0x34b655…2a6f
10 touches
10 conflicts
0x9365e097…ff56
0x34b655…2a6f
10 touches
10 conflicts
0x9901c9c3…4292
0x34b655…2a6f
10 touches
10 conflicts
0xa57576bb…e01f
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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity