← previous blocknext block →recent activity
Analyzing
Block #85,746,118
9 transactions · 9 stateful · 2026-07-05 10:52:31 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,746,118 · 9 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5986a78…c255
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3f36d66…28d4
0x065c9d…c394
3 touches
1 conflict
0x67848d75…7ace
0x065c9d…c394
3 touches
1 conflict
0xb586ca9f…67af
0x065c9d…c394
3 touches
1 conflict
0xde6e84ea…ca7d
0x065c9d…c394
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 0xd5986a78f8…1ec255
Audit this contract →
← previous block·next block →recent activity