pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,763,932
47 transactions · 33 stateful · 2026-05-15 13:51:21 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.45
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,763,932 · 47 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
1w02w13w24w05w36w18w111w213w014w115w223w024w126w027w128w229w330w431w532w633w734w844w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
8 touches
6 conflicts
0x161e1ca1…0fd7
0x34b655…2a6f
8 touches
6 conflicts
0x32ee90db…decc
0x34b655…2a6f
8 touches
6 conflicts
0x8db1e0f2…2fcf
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: 0x34b6552d…112a6f
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity