← previous blocknext block →recent activity
Analyzing
Block #80,309,183
28 transactions · 22 stateful · 2026-06-10 06:30:03 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,309,183 · 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
1w02w13w04w05w16w27w38w49w410w511w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x158accef…4c74
0xa6afd3…d132
10 touches
10 conflicts
0x3422ac7c…aa3c
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x2b093939…9084
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity