← previous blocknext block →recent activity
Analyzing
Block #85,973,354
24 transactions · 22 stateful · 2026-07-06 12:06:27 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,973,354 · 24 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
2w03w14w25w39w013w414w116w517w018w319w620w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x7e10454f…4d9e
0xa6afd3…d132
8 touches
6 conflicts
0xb43dc900…22f2
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xeb365853…d35e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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: Kuru Exchange: Market-WETH/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity