pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,034,219
46 transactions · 35 stateful · 2026-05-07 13:32:17 UTC
Parallelism
67/100
Blocked
77%
Avg conflicts / tx
2.11
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,034,219 · 46 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w39w511w513w133w434w536w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x388e001a…7e04
0x34b655…2a6f
12 touches
15 conflicts
0x88033b3b…bc11
0xd32edf…ff58
11 touches
15 conflicts
0xe7574014…95e2
0x34b655…2a6f
10 touches
10 conflicts
0x0f94ee4c…189e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 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: 0x34b6552d…112a6f
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity