← previous blocknext block →recent activity
Analyzing
Block #85,839,233
14 transactions · 13 stateful · 2026-07-05 21:12:32 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,839,233 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xdaa7c05d…4cce
0x065c9d…c394
4 touches
1 conflict
0xc86649aa…4dbb
0x065c9d…c394
3 touches
1 conflict
0xeb6b523d…e7ce
0x40c49f…2af0
3 touches
1 conflict
0x7d79fcad…2992
0x065c9d…c394
3 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
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