pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,223,549
42 transactions · 37 stateful · 2026-05-13 01:45:01 UTC
Parallelism
67/100
Blocked
73%
Avg conflicts / tx
2.36
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,223,549 · 42 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w110w011w112w115w016w117w218w319w420w522w225w326w427w528w329w430w531w136w940w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xf823e97f…2ee6
0x065c9d…c394
12 touches
15 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0x8be70a68…f039
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
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: 0x34b6552d…112a6f
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity