← previous blocknext block →recent activity
Analyzing
Block #80,328,327
20 transactions · 13 stateful · 2026-06-10 08:37:44 UTC
Parallelism
90/100
Blocked
8%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,328,327 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84f6ec33…8694
0x065c9d…c394
4 touches
1 conflict
0x5783d2a2…3fac
0x065c9d…c394
3 touches
1 conflict
0x857149b2…13e3
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x3e8f1748…1d56
0x065c9d…c394
2 touches
0 conflicts
0x525aebc9…81bf
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
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-MON/USDC
1 conflict on slot 0x84f6ec33ff…6a8694
Audit this contract →
← previous block·next block →recent activity