← previous blocknext block →recent activity
Analyzing
Block #85,843,863
11 transactions · 10 stateful · 2026-07-05 21:43:24 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,843,863 · 11 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
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x42d7dae9…9d05
0x065c9d…c394
4 touches
1 conflict
0x3a364bcd…6d03
0x065c9d…c394
3 touches
1 conflict
0x2a2d8fd2…7af4
0x065c9d…c394
3 touches
1 conflict
0x614036c4…496a
0x065c9d…c394
2 touches
0 conflicts
0x742a3103…52a6
0x065c9d…c394
2 touches
0 conflicts
0xc41a65cc…5db5
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity