← previous blocknext block →recent activity
Analyzing
Block #85,628,354
11 transactions · 11 stateful · 2026-07-04 21:47:05 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,628,354 · 11 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
0xac531742…d0e4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb49e6d56…806a
0x065c9d…c394
3 touches
1 conflict
0x31472859…5f40
0x065c9d…c394
3 touches
1 conflict
0x277db0e0…0eac
0x065c9d…c394
2 touches
0 conflicts
0x35f0efcf…0a42
0x065c9d…c394
2 touches
0 conflicts
0xf5f59da9…8d84
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
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 0xac53174283…4cd0e4
Audit this contract →
← previous block·next block →recent activity