← previous blocknext block →recent activity
Analyzing
Block #85,895,543
20 transactions · 15 stateful · 2026-07-06 03:27:40 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,895,543 · 20 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe8b2b406…cc96
0xd32edf…ff58
3 touches
1 conflict
0x1ace87c6…7d5d
0x065c9d…c394
2 touches
0 conflicts
0x2ecc27d7…f084
0x065c9d…c394
2 touches
0 conflicts
0x658ffd18…e73b
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xba8ffee0…95e9
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity