← previous blocknext block →recent activity
Analyzing
Block #85,761,322
14 transactions · 11 stateful · 2026-07-05 12:33:42 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,761,322 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f918e51…d9b2
0x065c9d…c394
6 touches
3 conflicts
0xa78c3f72…7194
0x065c9d…c394
5 touches
3 conflicts
0x2c76015a…90d9
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe7dce9e4…a5a0
0x065c9d…c394
3 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
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
3 conflicts on slot 0x5f918e5156…8bd9b2
Audit this contract →
← previous block·next block →recent activity