← previous blocknext block →recent activity
Analyzing
Block #82,667,362
13 transactions · 10 stateful · 2026-06-21 04:34:58 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,667,362 · 13 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x7320c756…27da
0x065c9d…c394
3 touches
1 conflict
0x0436c9df…c51c
0x065c9d…c394
3 touches
1 conflict
0xcea54b0f…d5c9
0x065c9d…c394
2 touches
0 conflicts
0xe13d07c6…325b
0x065c9d…c394
2 touches
0 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
2 touches
0 conflicts
0x34a1ee7e…fb20
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity