← previous blocknext block →recent activity
Analyzing
Block #80,251,047
35 transactions · 27 stateful · 2026-06-10 00:02:29 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,251,047 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w19w410w011w112w213w314w415w516w625w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
14 touches
21 conflicts
0x00000000…000b
0x90c374…be45
14 touches
21 conflicts
0x9f4e12e3…21c7
0x336ed4…c59c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xa87df366…0824
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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: 0x90c3747c…0ebe45
21 conflicts on slot 0x0000000000…00000a
Audit this contract →
← previous block·next block →recent activity