← previous blocknext block →recent activity
Analyzing
Block #85,960,137
12 transactions · 9 stateful · 2026-07-06 10:38:17 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,960,137 · 12 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd8163fa…bd7f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x68712797…8d48
0x065c9d…c394
3 touches
1 conflict
0x259ee052…b1f5
0x065c9d…c394
2 touches
0 conflicts
0x62ca69d5…6ed9
0x065c9d…c394
2 touches
0 conflicts
0x89bd8d84…1d1b
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xc4d7d705…6c21
0x065c9d…c394
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 0xdd8163fa72…1cbd7f
Audit this contract →
← previous block·next block →recent activity