← previous blocknext block →recent activity
Analyzing
Block #80,677,617
12 transactions · 11 stateful · 2026-06-11 23:26:55 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,677,617 · 12 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
2w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf16a3337…95e9
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x74d1da1d…1a22
0x065c9d…c394
3 touches
1 conflict
0xd3f4f6b8…d6bc
0x065c9d…c394
3 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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 0xf16a333739…b995e9
Audit this contract →
← previous block·next block →recent activity