← previous blocknext block →recent activity
Analyzing
Block #80,253,259
13 transactions · 10 stateful · 2026-06-10 00:17:13 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,253,259 · 13 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
1w02w13w24w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x36d366fe…7adc
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x7531e9d9…196d
0xa6afd3…d132
4 touches
1 conflict
0xd9eeeb16…bda7
0xa6afd3…d132
3 touches
1 conflict
0x184f90ec…79c7
0x40c49f…2af0
2 touches
0 conflicts
0x5f710177…d05b
0x40c49f…2af0
2 touches
0 conflicts
0xd072212d…cf13
0x40c49f…2af0
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity