← previous blocknext block →recent activity
Analyzing
Block #80,327,777
14 transactions · 13 stateful · 2026-06-10 08:34:04 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,327,777 · 14 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x99042705…4f03
0x065c9d…c394
2 touches
0 conflicts
0xbee9ec3b…910e
0x065c9d…c394
2 touches
0 conflicts
0xca84fcb6…53b5
0x065c9d…c394
2 touches
0 conflicts
0xd8b5c754…3097
0x065c9d…c394
2 touches
0 conflicts
0xe9ea77e5…327b
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity