← previous blocknext block →recent activity
Analyzing
Block #86,564,920
13 transactions · 8 stateful · 2026-07-09 05:58:08 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,564,920 · 13 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e8a572e…373f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa9b6caad…7845
0x065c9d…c394
3 touches
1 conflict
0x567d4fd3…a291
0x065c9d…c394
3 touches
1 conflict
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x8488f10f…9353
0x69df8a…6292
2 touches
0 conflicts
0x8488f10f…9354
0x69df8a…6292
2 touches
0 conflicts
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
1 conflict on slot 0x7e8a572ef9…23373f
Audit this contract →
← previous block·next block →recent activity