← previous blocknext block →recent activity
Analyzing
Block #85,168,645
14 transactions · 14 stateful · 2026-07-02 18:45:39 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,168,645 · 14 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
2w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85ae18ee…86a3
0x065c9d…c394
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x440d5150…20b7
0x065c9d…c394
3 touches
1 conflict
0xcaba4be8…96a9
0x065c9d…c394
3 touches
1 conflict
0x2e388122…f88c
0x065c9d…c394
3 touches
1 conflict
0xcdb1527c…fe98
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
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 0x85ae18ee51…0986a3
Audit this contract →
← previous block·next block →recent activity