← previous blocknext block →recent activity
Analyzing
Block #85,987,227
22 transactions · 21 stateful · 2026-07-06 13:39:13 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,987,227 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w010w311w112w113w214w315w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x934b15f1…b5a9
0x851145…3f07
6 touches
3 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x7a12283f…b18a
0x69df8a…6292
4 touches
1 conflict
0x915c095e…c1e5
0x69df8a…6292
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity