← previous blocknext block →recent activity
Analyzing
Block #86,324,578
43 transactions · 29 stateful · 2026-07-08 03:11:36 UTC
Parallelism
91/100
Blocked
34%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,324,578 · 43 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
1w02w15w07w011w112w017w119w121w022w123w224w025w128w135w238w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xcaa99db6…4ca5
0xd32edf…ff58
5 touches
3 conflicts
0x5956f21f…30fb
0x065c9d…c394
5 touches
3 conflicts
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
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