← previous blocknext block →recent activity
Analyzing
Block #80,252,163
15 transactions · 11 stateful · 2026-06-10 00:09:56 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,252,163 · 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36d366fe…7adc
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x70457855…ae61
0xa6afd3…d132
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0x5ff3595c…a5a0
0x754704…b603
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
1 conflict on slot 0x36d366fe30…fe7adc
Audit this contract →
← previous block·next block →recent activity