← previous blocknext block →recent activity
Analyzing
Block #85,963,301
10 transactions · 9 stateful · 2026-07-06 10:59:27 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,963,301 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b60b708…5b4b
0x69df8a…6292
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0xf7426a95…7462
0x065c9d…c394
3 touches
1 conflict
0x1dde5e6a…8b5e
0x69df8a…6292
2 touches
1 conflict
0x8916d1c5…8f0f
0x065c9d…c394
2 touches
1 conflict
0x11a4871a…43bc
0x69df8a…6292
2 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: MarginAccount
1 conflict on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity