← previous blocknext block →recent activity
Analyzing
Block #85,903,467
11 transactions · 10 stateful · 2026-07-06 04:20:29 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,903,467 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2e5a1932…426a
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x19159981…5204
0x065c9d…c394
3 touches
1 conflict
0x331a0c96…7611
0x065c9d…c394
2 touches
0 conflicts
0x8df86471…a6d9
0x065c9d…c394
2 touches
0 conflicts
0x99797a6e…4e91
0x065c9d…c394
2 touches
0 conflicts
0xa5e21cb5…bbf6
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity