pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,229,234
53 transactions · 34 stateful · 2026-05-13 02:22:45 UTC
Parallelism
70/100
Blocked
68%
Avg conflicts / tx
2.57
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #74,229,234 · 53 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1417w1420w1532w137w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3e124fd…11c5
0xd32edf…ff58
31 touches
120 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
10 touches
10 conflicts
0x768cffcd…2648
0x34b655…2a6f
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x07b5c6c6…886a
0x1b6862…e19c
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
120 conflicts on slot 0xd3e124fdf7…4f11c5
Audit this contract →
← previous block·next block →recent activity