← previous blocknext block →recent activity
Analyzing
Block #83,495,419
14 transactions · 12 stateful · 2026-06-25 00:48:17 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,495,419 · 14 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
1w03w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2886e2bc…6ab8
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9db7e12e…bdc8
0x065c9d…c394
4 touches
2 conflicts
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x0c8c031e…f90b
0x065c9d…c394
3 touches
1 conflict
0xc0889304…b0f0
0x065c9d…c394
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
6 conflicts on slot 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity