← previous blocknext block →recent activity
Analyzing
Block #86,851,607
28 transactions · 25 stateful · 2026-07-10 13:55:45 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,851,607 · 28 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
1w02w13w25w36w07w18w29w310w411w512w619w420w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xac808a27…82db
0x34b655…2a6f
8 touches
6 conflicts
0xf81d0d0f…cf78
0x34b655…2a6f
8 touches
6 conflicts
0xf94d24c1…5f81
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x006ee1d9…5485
0xa6afd3…d132
8 touches
6 conflicts
0xbcdee322…f454
0xa6afd3…d132
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