← previous blocknext block →recent activity
Analyzing
Block #80,761,049
11 transactions · 9 stateful · 2026-06-12 08:43:14 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,761,049 · 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
2 touches
1 conflict
0x1aaf1f2d…55cd
0x065c9d…c394
2 touches
0 conflicts
0xee7df7df…b9f8
0x065c9d…c394
2 touches
0 conflicts
0xaf41644f…8f2e
0x0c65a0…0852
2 touches
0 conflicts
0xc48c0c8f…eb55
0x0c65a0…0852
2 touches
0 conflicts
0x2bab24a6…c56d
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
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