pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,764,040
64 transactions · 46 stateful · 2026-05-15 13:52:04 UTC
Parallelism
70/100
Blocked
80%
Avg conflicts / tx
2.95
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,764,040 · 64 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
1w02w13w24w35w46w57w68w79w810w911w1018w1136w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x223f0765…b930
0xd32edf…ff58
23 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xd814f518…f5b4
0x34b655…2a6f
12 touches
15 conflicts
0x0d622e34…0000
0x681e90…ae09
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 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 0x223f076568…8eb930
Audit this contract →
← previous block·next block →recent activity