← previous blocknext block →recent activity
Analyzing
Block #85,751,252
7 transactions · 6 stateful · 2026-07-05 11:26:46 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,751,252 · 7 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
1w02w15w2
- 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
0x7f2a1f21…5842
0x065c9d…c394
3 touches
1 conflict
0x07f74bcc…6941
0x065c9d…c394
3 touches
1 conflict
0x2ad9bcfe…d77c
0x065c9d…c394
2 touches
0 conflicts
0x3021a222…32f5
0x065c9d…c394
2 touches
0 conflicts
0x7afd8ee5…2289
0x065c9d…c394
2 touches
0 conflicts
0x8cb4c4d7…7e15
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