← previous blocknext block →recent activity
Analyzing
Block #80,165,926
24 transactions · 20 stateful · 2026-06-09 14:34:47 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,165,926 · 24 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
3w04w19w010w111w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x37674bd8…8f35
0x34b655…2a6f
4 touches
1 conflict
0x36d366fe…7adc
0xa6afd3…d132
4 touches
1 conflict
0x19b24628…6303
0xd32edf…ff58
3 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x7531e9d9…196d
0xa6afd3…d132
2 touches
0 conflicts
0x0a4513f9…826e
0xea1b8e…c5ec
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