pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,401
54 transactions · 43 stateful · 2026-05-16 07:15:27 UTC
Parallelism
74/100
Blocked
77%
Avg conflicts / tx
2.57
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,920,401 · 54 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
1w02w13w24w35w46w57w68w79w811w215w318w420w536w937w1038w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x997af8ef…df12
0xd32edf…ff58
23 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xda6b535e…6d6c
0x1b6862…e19c
8 touches
6 conflicts
0x15c9b5bf…f732
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 0x997af8efef…ccdf12
Audit this contract →
← previous block·next block →recent activity