← previous blocknext block →recent activity
Analyzing
Block #80,754,236
106 transactions · 88 stateful · 2026-06-12 07:57:48 UTC
Parallelism
87/100
Blocked
77%
Avg conflicts / tx
3.23
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #80,754,236 · 106 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w312w413w119w525w527w628w230w732w839w1040w1141w1285w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
26 touches
78 conflicts
0x90f07a4f…d932
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xafa8d1d1…23eb
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0029
0x1b6862…e19c
18 touches
36 conflicts
0x0a6cb118…4ca4
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 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
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity