← previous blocknext block →recent activity
Analyzing
Block #80,825,864
36 transactions · 29 stateful · 2026-06-12 15:55:24 UTC
Parallelism
86/100
Blocked
52%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,825,864 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w010w011w112w213w314w415w019w120w321w422w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
10 touches
10 conflicts
0x0a53d503…0339
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e634
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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: 0x6fae9933…7ba56d
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity