← previous blocknext block →recent activity
Analyzing
Block #85,616,651
11 transactions · 10 stateful · 2026-07-04 20:29:10 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,616,651 · 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd3e8cf12…cd89
0x065c9d…c394
4 touches
1 conflict
0x8dff69a4…c88e
0x065c9d…c394
3 touches
1 conflict
0xd025db20…b18b
0x065c9d…c394
3 touches
1 conflict
0x1d8bb330…5f08
0x065c9d…c394
2 touches
0 conflicts
0x5183b86a…dced
0x065c9d…c394
2 touches
0 conflicts
0x9be82744…530a
0x065c9d…c394
2 touches
0 conflicts
0xc0a3af0c…6e59
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