← previous blocknext block →recent activity
Analyzing
Block #80,313,466
13 transactions · 11 stateful · 2026-06-10 06:58:39 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,313,466 · 13 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
1w02w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c93540d…6530
0x065c9d…c394
4 touches
1 conflict
0xd5b10148…e632
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8881e4ab…92b7
0xd32edf…ff58
3 touches
1 conflict
0x48a1c735…d4f1
0x065c9d…c394
2 touches
0 conflicts
0x632e1dcd…e204
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 0x0c93540db3…336530
Audit this contract →
← previous block·next block →recent activity