← previous blocknext block →recent activity
Analyzing
Block #86,659,313
47 transactions · 39 stateful · 2026-07-09 16:31:16 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.09
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,659,313 · 47 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w211w012w113w215w316w417w518w619w720w722w128w834w337w438w140w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
10 touches
10 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
10 touches
10 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
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