← previous blocknext block →recent activity
Analyzing
Block #85,704,914
14 transactions · 12 stateful · 2026-07-05 06:18:10 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,704,914 · 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe471e679…6149
0x065c9d…c394
4 touches
1 conflict
0xc6cadb9d…4778
0x065c9d…c394
3 touches
1 conflict
0x010158b8…28da
0x065c9d…c394
2 touches
0 conflicts
0x09470934…7d82
0x065c9d…c394
2 touches
0 conflicts
0x5a330c21…21dd
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x8cb82dbc…6877
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity