← previous blocknext block →recent activity
Analyzing
Block #85,546,313
8 transactions · 8 stateful · 2026-07-04 12:40:46 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,546,313 · 8 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x62d3136c…9712
0x065c9d…c394
4 touches
1 conflict
0x9be82744…530a
0x065c9d…c394
4 touches
1 conflict
0x5ee75cc5…1415
0x065c9d…c394
3 touches
1 conflict
0xaf3b7b30…b88c
0x065c9d…c394
3 touches
1 conflict
0x6686c70e…4faf
0x065c9d…c394
3 touches
1 conflict
0x57b66429…a95e
0x065c9d…c394
3 touches
1 conflict
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity