← previous blocknext block →recent activity
Analyzing
Block #85,753,078
7 transactions · 5 stateful · 2026-07-05 11:38:51 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,753,078 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xf6c29c45…fa7d
0x065c9d…c394
4 touches
1 conflict
0x859c9d9b…1ab8
0x065c9d…c394
3 touches
1 conflict
0x810e31b7…efbe
0x065c9d…c394
3 touches
1 conflict
0xafbd5368…9bff
0x065c9d…c394
3 touches
1 conflict
0x89f64deb…d16a
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity