← previous blocknext block →recent activity
Analyzing
Block #86,500,662
20 transactions · 14 stateful · 2026-07-08 22:48:10 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,500,662 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9df53651…e42d
0xd32edf…ff58
5 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xe2c76a27…7c35
0x065c9d…c394
3 touches
1 conflict
0x7c0cd99e…57f7
0x065c9d…c394
3 touches
1 conflict
0x2fc00d19…1333
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