← previous blocknext block →recent activity
Analyzing
Block #80,291,779
12 transactions · 12 stateful · 2026-06-10 04:34:03 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,291,779 · 12 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
2 conflicts
0x489cb750…7069
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc1b6b432…8177
0x065c9d…c394
2 touches
0 conflicts
0xc5bccdaa…75dc
0x065c9d…c394
2 touches
0 conflicts
0xd9c92b32…f6c6
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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
2 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity