← previous blocknext block →recent activity
Analyzing
Block #80,157,640
28 transactions · 20 stateful · 2026-06-09 13:39:29 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,157,640 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w27w39w210w411w412w513w619w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6b917f…3a72
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb0e9898d…42c2
0xa6afd3…d132
8 touches
6 conflicts
0xaf006bb2…3f20
0xd32edf…ff58
7 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x4d42f16e…a6cc
0x1b6862…e19c
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 0xde6b917faa…a83a72
Audit this contract →
← previous block·next block →recent activity