← previous blocknext block →recent activity
Analyzing
Block #86,659,133
52 transactions · 39 stateful · 2026-07-09 16:30:04 UTC
Parallelism
58/100
Blocked
82%
Avg conflicts / tx
3.25
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #86,659,133 · 52 txs across 22 waves · depth 22
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
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w39w410w511w219w020w121w222w337w238w140w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0xca2926e0…61b5
0x34b655…2a6f
14 touches
21 conflicts
0x0d0d2659…e1f2
0x34b655…2a6f
14 touches
21 conflicts
0x3230277c…ef39
0xc8689a…ee79
14 touches
21 conflicts
0x044844a0…7418
0x34b655…2a6f
14 touches
21 conflicts
0xba769ff1…458f
0x34b655…2a6f
14 touches
21 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
14 touches
21 conflicts
0xcf82b696…8a97
0xd32edf…ff58
11 touches
15 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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity