← previous blocknext block →recent activity
Analyzing
Block #80,309,582
28 transactions · 19 stateful · 2026-06-10 06:32:42 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,309,582 · 28 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
3w04w07w18w211w112w217w324w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0dcd3d25…731b
0xd32edf…ff58
5 touches
3 conflicts
0xd89f212d…2bbf
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd9c4ecc…1903
0x065c9d…c394
3 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
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
3 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity