← previous blocknext block →recent activity
Analyzing
Block #80,408,298
23 transactions · 20 stateful · 2026-06-10 17:30:35 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,408,298 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w39w015w421w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe41f8863…29a4
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xed863ec8…90d9
0x1b6862…e19c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 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: 0xa6afd386…b0d132
6 conflicts on slot 0xe41f886384…3929a4
Audit this contract →
← previous block·next block →recent activity