← previous blocknext block →recent activity
Analyzing
Block #80,292,684
23 transactions · 18 stateful · 2026-06-10 04:40:04 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,292,684 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w06w17w18w29w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x5cc231f5…f1cd
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6a9d
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6aa0
0x69df8a…6292
4 touches
1 conflict
0xed7dd7db…6022
0x69df8a…6292
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0xe41f8863…29a4
0xa6afd3…d132
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity