← previous blocknext block →recent activity
Analyzing
Block #80,254,404
20 transactions · 18 stateful · 2026-06-10 00:24:50 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,254,404 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w48w59w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f1e40f…09a3
0x3bd359…433a
10 touches
10 conflicts
0x527f20e3…82e7
0x754704…b603
10 touches
10 conflicts
0x36d366fe…7adc
0xa6afd3…d132
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x84611dd3…b348
0x1b6862…e19c
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: Wrapped MON (WMON)
10 conflicts on slot 0xd9f1e40f03…3209a3
Audit this contract →
← previous block·next block →recent activity