← previous blocknext block →recent activity
Analyzing
Block #82,538,254
20 transactions · 16 stateful · 2026-06-20 14:10:00 UTC
Parallelism
85/100
Blocked
19%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,538,254 · 20 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
1w06w110w012w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1b3114cd…5e2d
0xa6afd3…d132
4 touches
1 conflict
0x66c5e348…51d0
0xa6afd3…d132
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x10f76cb2…696a
0x34b655…2a6f
2 touches
0 conflicts
0x36bca823…4e62
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
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-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity