← previous blocknext block →recent activity
Analyzing
Block #85,995,080
25 transactions · 18 stateful · 2026-07-06 14:31:44 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,995,080 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w016w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x112cf8ad…6e4f
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa1ea167e…9aad
0xa6afd3…d132
4 touches
1 conflict
0xed1f5095…0f59
0xa6afd3…d132
3 touches
1 conflict
0x7a8f3356…31f0
0xa6afd3…d132
3 touches
1 conflict
0x22a5f665…39b1
0x40c49f…2af0
2 touches
0 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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x112cf8adc5…856e4f
Audit this contract →
← previous block·next block →recent activity