pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,565,969
58 transactions · 35 stateful · 2026-05-14 15:49:03 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
2.71
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,565,969 · 58 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w912w1013w1114w1216w1317w1418w1519w1621w527w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5fa30a6…ad86
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…0000
0x1f86a9…17ed
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0xb02fe354…948e
0x3bd359…433a
12 touches
15 conflicts
0x6aa624fd…a851
0x1b6862…e19c
12 touches
15 conflicts
0xb02fe354…948e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
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: 0xd32edf66…9fff58
136 conflicts on slot 0xf5fa30a6e9…e4ad86
Audit this contract →
← previous block·next block →recent activity