← previous blocknext block →recent activity
Analyzing
Block #85,754,151
17 transactions · 10 stateful · 2026-07-05 11:46:00 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,754,151 · 17 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
4w05w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x131cb7c9…5da2
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x8e3535bd…e1b7
0x065c9d…c394
4 touches
1 conflict
0xaaa31da8…b680
0x065c9d…c394
3 touches
1 conflict
0x2df22663…c515
0x065c9d…c394
3 touches
1 conflict
0x4644705f…3228
0x065c9d…c394
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity