← previous blocknext block →recent activity
Analyzing
Block #85,504,500
14 transactions · 10 stateful · 2026-07-04 08:02:26 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,504,500 · 14 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
7w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x365697f4…32c8
0x065c9d…c394
4 touches
1 conflict
0xfb3e4ba4…5e10
0x065c9d…c394
4 touches
1 conflict
0x0b3a72d1…718e
0x065c9d…c394
4 touches
1 conflict
0x666013fb…ebe6
0x065c9d…c394
3 touches
1 conflict
0x0aff32f0…aa80
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 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity