← previous blocknext block →recent activity
Analyzing
Block #80,167,010
32 transactions · 28 stateful · 2026-06-09 14:42:01 UTC
Parallelism
69/100
Blocked
68%
Avg conflicts / tx
2.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,167,010 · 32 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
1w02w13w04w16w07w18w29w310w411w514w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c5
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: Perpl
36 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity