← previous blocknext block →recent activity
Analyzing
Block #85,968,333
15 transactions · 13 stateful · 2026-07-06 11:32:57 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,968,333 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xeccb66a5…fba8
0xd32edf…ff58
3 touches
1 conflict
0xa71609aa…87df
0x065c9d…c394
3 touches
1 conflict
0x323b78af…9e19
0x065c9d…c394
3 touches
1 conflict
0x66007d3e…672e
0x065c9d…c394
3 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 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity