← previous blocknext block →recent activity
Analyzing
Block #80,103,623
12 transactions · 10 stateful · 2026-06-09 07:39:47 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,103,623 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x5f0d3a01…91c7
0x699abc…6a3b
4 touches
1 conflict
0x9427948b…edca
0x699abc…6a3b
4 touches
1 conflict
0xdf3fc032…8967
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
2 touches
0 conflicts
0x0859dc2d…7b01
0x131a2e…0da9
2 touches
0 conflicts
0x0859dc2d…7b02
0x131a2e…0da9
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: AUSD (AUSD)
1 conflict on slot 0x335a161d76…bdfe7f
Audit this contract →
← previous block·next block →recent activity