← previous blocknext block →recent activity
Analyzing
Block #85,933,346
9 transactions · 9 stateful · 2026-07-06 07:39:37 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,933,346 · 9 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x83ef20fe…0b5d
0x065c9d…c394
3 touches
1 conflict
0x173a7417…15d7
0x065c9d…c394
3 touches
1 conflict
0xc0f39a23…1219
0x065c9d…c394
3 touches
1 conflict
0x02b4ac17…61b3
0x065c9d…c394
3 touches
1 conflict
0x1865a8aa…42c4
0x065c9d…c394
3 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity