pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,454,388
67 transactions · 48 stateful · 2026-05-14 03:20:42 UTC
Parallelism
72/100
Blocked
77%
Avg conflicts / tx
2.87
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,454,388 · 67 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
1w02w13w24w35w414w315w416w517w648w549w654w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x304d7ace…1387
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
14 touches
21 conflicts
0xc1baef71…068a
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x0de7749d…5bef
0x34b655…2a6f
14 touches
21 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: 0x34b6552d…112a6f
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity