← previous blocknext block →recent activity
Analyzing
Block #80,754,083
17 transactions · 10 stateful · 2026-06-12 07:56:46 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,754,083 · 17 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
1w02w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf47bc1b7…8eda
0x065c9d…c394
3 touches
1 conflict
0x81e97f56…b5c3
0x065c9d…c394
3 touches
1 conflict
0x8adce664…bb7e
0x065c9d…c394
3 touches
1 conflict
0x51826aec…8225
0x065c9d…c394
3 touches
1 conflict
0x59c7fbfc…4ad9
0x065c9d…c394
3 touches
1 conflict
0xcc1ebb05…308d
0x065c9d…c394
3 touches
1 conflict
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity