← previous blocknext block →recent activity
Analyzing
Block #80,256,450
10 transactions · 9 stateful · 2026-06-10 00:38:29 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,256,450 · 10 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfa47797…d420
0x065c9d…c394
3 touches
1 conflict
0x21892e76…210f
0x065c9d…c394
3 touches
1 conflict
0x2f4c8523…f788
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0004
0x170763…067c
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x46ea6f…1291
2 touches
0 conflicts
0x00000000…0004
0x57d25c…30d1
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