← previous blocknext block →recent activity
Analyzing
Block #86,851,115
40 transactions · 28 stateful · 2026-07-10 13:52:27 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,851,115 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w19w210w311w412w013w114w215w317w418w521w322w423w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x17d94c79…2463
0x34b655…2a6f
8 touches
6 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0x414ca622…37ab
0x34b655…2a6f
8 touches
6 conflicts
0x428b6e5b…8909
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity