← previous blocknext block →recent activity
Analyzing
Block #86,850,061
35 transactions · 27 stateful · 2026-07-10 13:45:25 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.31
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,850,061 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w211w112w013w114w215w316w418w519w626w327w128w729w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
10 touches
10 conflicts
0xbcdee322…f454
0xa6afd3…d132
8 touches
6 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
8 touches
6 conflicts
0x7d64cfc8…6cd5
0x34b655…2a6f
8 touches
6 conflicts
0x826cce18…251c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 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