pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,764,031
65 transactions · 43 stateful · 2026-05-15 13:52:00 UTC
Parallelism
66/100
Blocked
81%
Avg conflicts / tx
3
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #74,764,031 · 65 txs across 22 waves · depth 22
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
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w210w011w115w218w319w322w346w447w550w453w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x388e001a…7e04
0x34b655…2a6f
20 touches
45 conflicts
0x3582b315…0ce0
0x34b655…2a6f
12 touches
15 conflicts
0xe863dc4c…205c
0xd32edf…ff58
11 touches
15 conflicts
0x928d6b23…536f
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
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: 0x34b6552d…112a6f
66 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity