pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,073
70 transactions · 43 stateful · 2026-05-15 13:59:00 UTC
Parallelism
81/100
Blocked
67%
Avg conflicts / tx
1.77
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,765,073 · 70 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w012w015w117w221w122w223w029w132w134w237w348w449w551w653w756w858w362w963w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1864b9e3…0b43
0xd32edf…ff58
21 touches
55 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0xedb848fe…6534
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
55 conflicts on slot 0x1864b9e3a5…a40b43
Audit this contract →
← previous block·next block →recent activity