pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,239,350
46 transactions · 32 stateful · 2026-05-13 03:30:04 UTC
Parallelism
72/100
Blocked
75%
Avg conflicts / tx
1.74
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,239,350 · 46 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w39w610w416w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x768cffcd…2648
0x34b655…2a6f
14 touches
21 conflicts
0xce8bbe33…b72e
0x3bd359…433a
12 touches
15 conflicts
0x6af306bb…2e81
0x3bd359…433a
12 touches
15 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
12 touches
15 conflicts
0x590a2752…5f3e
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xf823e97f…2ee6
0x065c9d…c394
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: 0x065c9d28…a9c394
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity