← previous blocknext block →recent activity
Analyzing
Block #80,312,557
21 transactions · 18 stateful · 2026-06-10 06:52:35 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,312,557 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w09w111w212w313w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x158accef…4c74
0xa6afd3…d132
12 touches
15 conflicts
0x40970e69…da50
0x69df8a…6292
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
10 touches
10 conflicts
0xdb067026…9eb8
0x69df8a…6292
10 touches
10 conflicts
0xe41f8863…29a4
0xa6afd3…d132
10 touches
10 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
10 touches
10 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