← previous blocknext block →recent activity
Analyzing
Block #82,018,728
23 transactions · 21 stateful · 2026-06-18 04:24:52 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,018,728 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w112w216w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa743c8dd…ebf2
0x788571…8888
6 touches
3 conflicts
0x797464db…e15a
0x788571…8888
6 touches
3 conflicts
0x00000000…0000
0x24b18e…3301
6 touches
3 conflicts
0x00000000…0001
0x24b18e…3301
6 touches
3 conflicts
0x771a3650…01cd
0x3bd359…433a
6 touches
3 conflicts
0xc72a8432…127e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 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-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity