← previous blocknext block →recent activity
Analyzing
Block #82,656,623
23 transactions · 17 stateful · 2026-06-21 03:22:55 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,656,623 · 23 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
2w03w04w05w16w010w212w116w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa29182a1…c12c
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x7e10454f…4d9e
0xa6afd3…d132
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0028
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-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity