← previous blocknext block →recent activity
Analyzing
Block #83,495,693
22 transactions · 20 stateful · 2026-06-25 00:50:07 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,495,693 · 22 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
1w02w13w25w17w09w110w011w112w216w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0x27b60bfc…8285
0xd32edf…ff58
5 touches
3 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x1c7763f6…89be
0x34b655…2a6f
4 touches
1 conflict
0xd406be52…9094
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity