← previous blocknext block →recent activity
Analyzing
Block #82,656,234
14 transactions · 10 stateful · 2026-06-21 03:20:19 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,656,234 · 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x0dc3646f…8020
0x065c9d…c394
4 touches
1 conflict
0x5996c396…286d
0x065c9d…c394
3 touches
1 conflict
0x7b5ce212…4193
0x065c9d…c394
3 touches
1 conflict
0x508f9ae2…6bcf
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x7edea1b6…d90a
0x34b655…2a6f
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity