← previous blocknext block →recent activity
Analyzing
Block #82,159,046
13 transactions · 10 stateful · 2026-06-18 20:00:53 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,159,046 · 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
1w02w13w24w28w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b3114cd…5e2d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…000b
0x097d40…9920
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
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 0x1b3114cdec…355e2d
Audit this contract →
← previous block·next block →recent activity