← previous blocknext block →recent activity
Analyzing
Block #86,215,769
20 transactions · 18 stateful · 2026-07-07 15:04:58 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,215,769 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w18w29w310w411w513w015w016w117w218w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdec5bfea…d17f
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x202c03eb…cf33
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x6f7a92ed…5651
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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 0xdec5bfea10…c4d17f
Audit this contract →
← previous block·next block →recent activity