← previous blocknext block →recent activity
Analyzing
Block #80,290,072
11 transactions · 9 stateful · 2026-06-10 04:22:39 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,290,072 · 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
0x68da1a55…c4ba
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcd5e8a16…87f1
0x065c9d…c394
3 touches
1 conflict
0x1f266245…4bd0
0x065c9d…c394
3 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
2 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x06e40499…165e
0x69df8a…6292
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 0x68da1a55e5…85c4ba
Audit this contract →
← previous block·next block →recent activity