← previous blocknext block →recent activity
Analyzing
Block #83,480,285
14 transactions · 13 stateful · 2026-06-24 23:07:30 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,480,285 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff2b017…3fa2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc5e76624…b742
0x065c9d…c394
3 touches
1 conflict
0x671d232e…1aed
0x065c9d…c394
3 touches
1 conflict
0x24fce1d0…cbad
0x065c9d…c394
3 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