← previous blocknext block →recent activity
Analyzing
Block #86,965,263
28 transactions · 22 stateful · 2026-07-11 02:35:32 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,965,263 · 28 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
2w03w14w05w110w011w114w015w017w218w121w322w426w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
10 touches
10 conflicts
0xc7a15219…7745
0xa6afd3…d132
10 touches
10 conflicts
0xb06917e8…6985
0x34b655…2a6f
8 touches
6 conflicts
0x7b3da897…b268
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xd49ae013…88ac
0x34b655…2a6f
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