← previous blocknext block →recent activity
Analyzing
Block #85,751,081
9 transactions · 9 stateful · 2026-07-05 11:25:38 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,751,081 · 9 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4a7e91bb…d690
0x065c9d…c394
4 touches
1 conflict
0x59413ff7…57cd
0x065c9d…c394
4 touches
1 conflict
0x798a688e…cbf4
0x065c9d…c394
4 touches
1 conflict
0x7f2a1f21…5842
0x065c9d…c394
3 touches
1 conflict
0x46b9a1c0…816d
0x065c9d…c394
3 touches
1 conflict
0x45f562b2…9294
0x69df8a…6292
2 touches
0 conflicts
0x8488f10f…9353
0x69df8a…6292
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