← previous blocknext block →recent activity
Analyzing
Block #80,140,458
11 transactions · 9 stateful · 2026-06-09 11:45:00 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,140,458 · 11 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
1w02w13w2
- 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
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x1338b9e5…b467
0x065c9d…c394
2 touches
0 conflicts
0x26e1da33…4b7b
0x065c9d…c394
2 touches
0 conflicts
0x28a92873…d0a4
0x065c9d…c394
2 touches
0 conflicts
0x68eff951…a9a4
0x065c9d…c394
2 touches
0 conflicts
0xa5c21e20…60ca
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
3 conflicts on slot 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity