pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,260
45 transactions · 36 stateful · 2026-05-16 07:14:30 UTC
Parallelism
78/100
Blocked
64%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,920,260 · 45 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w07w08w112w113w214w015w016w117w220w021w122w223w325w326w429w532w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xb9868b52…c77f
0x34b655…2a6f
12 touches
15 conflicts
0x550d3da6…80d8
0xd32edf…ff58
11 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf35dca9e…bd8d
0x1b6862…e19c
6 touches
3 conflicts
0x0a809ce1…7894
0x34b655…2a6f
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