← previous blocknext block →recent activity
Analyzing
Block #85,219,232
12 transactions · 12 stateful · 2026-07-03 00:22:34 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,219,232 · 12 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xfa7f7e41…4a91
0x065c9d…c394
4 touches
1 conflict
0x5bb88c5d…4e65
0x065c9d…c394
4 touches
1 conflict
0x5dabed30…5df6
0x065c9d…c394
4 touches
1 conflict
0x1b656cd4…cbba
0x065c9d…c394
3 touches
1 conflict
0xc9dcb29a…06af
0x065c9d…c394
3 touches
1 conflict
0x37c72622…f8c9
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity