← previous blocknext block →recent activity
Analyzing
Block #92,006,951
32 transactions · 27 stateful · 2026-07-31 20:05:53 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,006,951 · 32 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
4w05w16w28w012w013w114w216w317w418w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xd121bc24…efd8
0x7b9256…1fb2
6 touches
3 conflicts
0xd121bc24…efd9
0x7b9256…1fb2
6 touches
3 conflicts
0xd121bc24…efdc
0x7b9256…1fb2
6 touches
3 conflicts
0xeb85de79…3e7c
0x7b9256…1fb2
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity