← previous blocknext block →recent activity
Analyzing
Block #85,221,261
22 transactions · 18 stateful · 2026-07-03 00:36:03 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,221,261 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w112w013w114w115w216w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd7aab76f…e16f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0x9cc13b7b…c0ac
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 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: Market-MON/USDC
3 conflicts on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity