← previous blocknext block →recent activity
Analyzing
Block #80,330,169
29 transactions · 20 stateful · 2026-06-10 08:49:58 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,330,169 · 29 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
1w02w03w14w25w06w17w08w312w114w415w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
8 touches
6 conflicts
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity