← previous blocknext block →recent activity
Analyzing
Block #80,328,621
34 transactions · 22 stateful · 2026-06-10 08:39:41 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,328,621 · 34 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
1w02w13w27w08w29w314w417w521w231w032w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b9a42f7…7b88
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xe41f8863…29a4
0xa6afd3…d132
6 touches
3 conflicts
0xab2a87f1…eafc
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
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
10 conflicts on slot 0x7b9a42f78b…5e7b88
Audit this contract →
← previous block·next block →recent activity