← previous blocknext block →recent activity
Analyzing
Block #80,654,370
39 transactions · 28 stateful · 2026-06-11 20:51:59 UTC
Parallelism
74/100
Blocked
75%
Avg conflicts / tx
2.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,654,370 · 39 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w512w624w732w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
20 touches
45 conflicts
0xf7df2415…c32b
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x14af78bb…aedd
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2c7e941d…5f72
0x34b655…2a6f
4 touches
1 conflict
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: 0x6fae9933…7ba56d
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity