← previous blocknext block →recent activity
Analyzing
Block #86,965,167
20 transactions · 20 stateful · 2026-07-11 02:34:55 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,965,167 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w512w013w514w619w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x36890fff…f3d1
0x34b655…2a6f
10 touches
10 conflicts
0xa2ec331b…6100
0x34b655…2a6f
10 touches
10 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
8 touches
6 conflicts
0x40883ce5…2ae2
0x34b655…2a6f
8 touches
6 conflicts
0x63546690…2c97
0x34b655…2a6f
8 touches
6 conflicts
0x775a8ad3…8307
0x34b655…2a6f
8 touches
6 conflicts
0x9355efee…7bcd
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity