← previous blocknext block →recent activity
Analyzing
Block #85,505,051
13 transactions · 11 stateful · 2026-07-04 08:06:05 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,505,051 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb3e4ba4…5e10
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9edce0ee…6d89
0x065c9d…c394
5 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x19d6f4fc…bee2
0x065c9d…c394
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x627f9dd9…cf99
0x065c9d…c394
3 touches
1 conflict
0x40b02e55…1041
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
3 conflicts on slot 0xfb3e4ba404…8f5e10
Audit this contract →
← previous block·next block →recent activity