← previous blocknext block →recent activity
Analyzing
Block #85,601,462
10 transactions · 10 stateful · 2026-07-04 18:48:09 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,601,462 · 10 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3c633fa…b64e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb1fbebee…2c75
0x065c9d…c394
3 touches
1 conflict
0x1a5415ef…ad2c
0x065c9d…c394
3 touches
1 conflict
0x3897e13e…c4a3
0x065c9d…c394
2 touches
0 conflicts
0x9022787c…fc4a
0x065c9d…c394
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
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 0xf3c633fa00…c8b64e
Audit this contract →
← previous block·next block →recent activity