← previous blocknext block →recent activity
Analyzing
Block #85,177,614
21 transactions · 18 stateful · 2026-07-02 19:45:22 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,177,614 · 21 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
2w04w05w16w07w19w014w216w317w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x89f64deb…d16a
0x065c9d…c394
4 touches
1 conflict
0xaf10c5a2…c4e7
0x065c9d…c394
4 touches
1 conflict
0x8bb179a3…dac3
0x5afd3e…7620
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity