← previous blocknext block →recent activity
Analyzing
Block #85,966,924
16 transactions · 15 stateful · 2026-07-06 11:23:36 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,966,924 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w210w311w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2cd2a965…5201
0xd32edf…ff58
3 touches
1 conflict
0x6b672a72…325c
0x065c9d…c394
2 touches
0 conflicts
0x8eb8e937…7b27
0x065c9d…c394
2 touches
0 conflicts
0xb3cac0ad…5ebb
0x065c9d…c394
2 touches
0 conflicts
0xe03f8144…28a7
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity