← previous blocknext block →recent activity
Analyzing
Block #80,329,057
28 transactions · 19 stateful · 2026-06-10 08:42:34 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,329,057 · 28 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
5w06w19w010w111w215w217w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4afaa2f…3b69
0xa6afd3…d132
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa743c8dd…ebf2
0x788571…8888
6 touches
3 conflicts
0x797464db…e15a
0x788571…8888
6 touches
3 conflicts
0x771a3650…01cd
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x24b18e…3301
6 touches
3 conflicts
0x00000000…0001
0x24b18e…3301
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
3 conflicts on slot 0xe4afaa2f27…943b69
Audit this contract →
← previous block·next block →recent activity