← previous blocknext block →recent activity
Analyzing
Block #86,788,016
15 transactions · 13 stateful · 2026-07-10 06:50:39 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,788,016 · 15 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
2w04w05w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0xfd5923dd…21b6
0x065c9d…c394
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xe25f56e1…e7aa
0x065c9d…c394
3 touches
1 conflict
0xb0ef7f02…dca4
0x065c9d…c394
3 touches
1 conflict
0x28f09725…2a4e
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity