← previous blocknext block →recent activity
Analyzing
Block #80,166,414
16 transactions · 10 stateful · 2026-06-09 14:38:02 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,166,414 · 16 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3f24874…1fb6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x36f1c548…0495
0x065c9d…c394
3 touches
1 conflict
0x0cc93dcb…9af1
0x065c9d…c394
2 touches
0 conflicts
0x229fbdfd…bd9c
0x065c9d…c394
2 touches
0 conflicts
0x7b408c52…67fa
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xd3f248741f…071fb6
Audit this contract →
← previous block·next block →recent activity