← previous blocknext block →recent activity
Analyzing
Block #82,803,409
15 transactions · 11 stateful · 2026-06-21 19:43:14 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,803,409 · 15 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
1w04w05w16w07w18w210w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8a751d7a…247c
0xa6afd3…d132
4 touches
1 conflict
0x9fb55ee7…8ecc
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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