← previous blocknext block →recent activity
Analyzing
Block #80,253,393
16 transactions · 14 stateful · 2026-06-10 00:18:07 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,253,393 · 16 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
2w03w04w15w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x36d366fe…7adc
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7531e9d9…196d
0xa6afd3…d132
4 touches
1 conflict
0xb28dfa8b…da7e
0xa6afd3…d132
4 touches
1 conflict
0x4c035f36…c744
0xa6afd3…d132
3 touches
1 conflict
0x7d07e58b…11c1
0xa6afd3…d132
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity