← previous blocknext block →recent activity
Analyzing
Block #80,164,766
28 transactions · 26 stateful · 2026-06-09 14:27:03 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,164,766 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w18w29w310w412w218w320w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36d366fe…7adc
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
6 touches
3 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
15 conflicts on slot 0x36d366fe30…fe7adc
Audit this contract →
← previous block·next block →recent activity