← previous blocknext block →recent activity
Analyzing
Block #85,907,500
17 transactions · 12 stateful · 2026-07-06 04:47:21 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,907,500 · 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x69b6e4e8…0c5e
0x065c9d…c394
4 touches
1 conflict
0x5132d533…5991
0x065c9d…c394
2 touches
0 conflicts
0xc0c05232…75f3
0x065c9d…c394
2 touches
0 conflicts
0xea8711a6…be99
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity