← previous blocknext block →recent activity
Analyzing
Block #85,679,448
10 transactions · 8 stateful · 2026-07-05 03:27:12 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,679,448 · 10 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a8046f…1317
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09d7fe0f…209b
0x065c9d…c394
3 touches
1 conflict
0x9379ddaa…2f29
0x065c9d…c394
3 touches
1 conflict
0x326dcea2…a019
0x0c65a0…0852
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
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 0x27a8046ffb…411317
Audit this contract →
← previous block·next block →recent activity