pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,332,236
50 transactions · 36 stateful · 2026-05-13 13:47:44 UTC
Parallelism
68/100
Blocked
81%
Avg conflicts / tx
2.34
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #74,332,236 · 50 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w719w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0x8e635fff…32f7
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xe4c6b0cb…0a20
0x1b6862…e19c
14 touches
21 conflicts
0x525b3d52…ade3
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity