← previous blocknext block →recent activity
Analyzing
Block #80,220,119
9 transactions · 5 stateful · 2026-06-09 20:36:13 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,220,119 · 9 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
1w02w14w2
- 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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x16bf80de…c56b
0x065c9d…c394
2 touches
0 conflicts
0xcf4c2f0a…a523
0x065c9d…c394
2 touches
0 conflicts
0xd4687342…ff39
0x065c9d…c394
2 touches
0 conflicts
0xf4c47139…d030
0x065c9d…c394
2 touches
0 conflicts
0xf8489613…bc8d
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity