← previous blocknext block →recent activity
Analyzing
Block #80,252,170
24 transactions · 22 stateful · 2026-06-10 00:09:59 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,252,170 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w29w210w311w314w017w422w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36d366fe…7adc
0xa6afd3…d132
8 touches
6 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x3c0d2f30…1afb
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x36d366fe30…fe7adc
Audit this contract →
← previous block·next block →recent activity