← previous blocknext block →recent activity
Analyzing
Block #85,752,271
21 transactions · 15 stateful · 2026-07-05 11:33:33 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,752,271 · 21 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
1w07w115w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77991f1a…56d5
0x065c9d…c394
4 touches
1 conflict
0xaf10c5a2…c4e7
0x065c9d…c394
4 touches
1 conflict
0xaaa31da8…b680
0x065c9d…c394
4 touches
1 conflict
0x8a8a690b…096f
0x065c9d…c394
3 touches
1 conflict
0x5497531e…4d79
0x065c9d…c394
3 touches
1 conflict
0x307c6cf7…adfb
0x065c9d…c394
3 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-MON/USDC
3 conflicts on slot 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity