← previous blocknext block →recent activity
Analyzing
Block #85,972,175
21 transactions · 19 stateful · 2026-07-06 11:58:34 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,972,175 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w310w011w413w514w118w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7c191216…2931
0xd32edf…ff58
5 touches
3 conflicts
0xae197bf5…c764
0x065c9d…c394
4 touches
1 conflict
0xe4cebef1…98a5
0x065c9d…c394
4 touches
1 conflict
0xe7e01fa9…fec0
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 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
6 conflicts on slot 0xce827910a4…82ff22
Audit this contract →
← previous block·next block →recent activity