← previous blocknext block →recent activity
Analyzing
Block #80,138,734
12 transactions · 10 stateful · 2026-06-09 11:33:30 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,138,734 · 12 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9d49c624…12c0
0x065c9d…c394
4 touches
1 conflict
0x0df45cb7…aa87
0x065c9d…c394
2 touches
0 conflicts
0x369bd210…395b
0x065c9d…c394
2 touches
0 conflicts
0x461b437b…f2fc
0x065c9d…c394
2 touches
0 conflicts
0x5c8809d8…4de2
0x065c9d…c394
2 touches
0 conflicts
0x74741cbe…453c
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity