← previous blocknext block →recent activity
Analyzing
Block #80,250,676
14 transactions · 13 stateful · 2026-06-10 00:00:00 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,250,676 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0xf8c8f189…e27e
0xd32edf…ff58
3 touches
1 conflict
0xe0ad6be9…fde1
0x065c9d…c394
3 touches
1 conflict
0x6fe66d0a…bcf3
0x065c9d…c394
3 touches
1 conflict
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0x13a54fa2…5ae3
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
3 conflicts on slot 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity