pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,235
60 transactions · 37 stateful · 2026-05-15 14:00:05 UTC
Parallelism
80/100
Blocked
70%
Avg conflicts / tx
1.7
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,765,235 · 60 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w619w1023w131w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cdf6c08…c344
0xd32edf…ff58
23 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xd25997d0…a685
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 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: 0xd32edf66…9fff58
66 conflicts on slot 0x0cdf6c080e…03c344
Audit this contract →
← previous block·next block →recent activity