← previous blocknext block →recent activity
Analyzing
Block #80,328,108
26 transactions · 20 stateful · 2026-06-10 08:36:16 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,328,108 · 26 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
1w02w13w24w35w49w510w011w117w023w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0x9a54f439…de63
0x34b655…2a6f
6 touches
3 conflicts
0x92265121…fb96
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x2d8a4b6f…1771
0x065c9d…c394
6 touches
3 conflicts
0x9ad5e87d…b1d2
0xd32edf…ff58
5 touches
3 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-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity