← previous blocknext block →recent activity
Analyzing
Block #86,565,138
17 transactions · 14 stateful · 2026-07-09 05:59:37 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,565,138 · 17 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
2w09w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x5602dd42…48f3
0x065c9d…c394
3 touches
1 conflict
0xda36c81c…a2e4
0x065c9d…c394
3 touches
1 conflict
0xd580b132…ad31
0x065c9d…c394
3 touches
1 conflict
0xc49e3f01…b2c3
0x065c9d…c394
3 touches
1 conflict
0x1e48811e…2e39
0x34b655…2a6f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity