← previous blocknext block →recent activity
Analyzing
Block #80,502,317
36 transactions · 27 stateful · 2026-06-11 03:56:58 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,502,317 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w07w08w19w210w311w412w516w526w630w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
12 touches
15 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
0x40970e69…da50
0x69df8a…6292
10 touches
10 conflicts
0x123e0bb6…7040
0xd32edf…ff58
9 touches
10 conflicts
0x52d65d97…1c96
0xa6afd3…d132
8 touches
6 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity