pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,772,261
66 transactions · 45 stateful · 2026-05-15 14:47:11 UTC
Parallelism
79/100
Blocked
76%
Avg conflicts / tx
2.15
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,772,261 · 66 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
1w02w13w24w05w16w27w08w19w210w311w412w513w618w132w240w341w342w456w357w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
20 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0x388e001a…7e04
0x34b655…2a6f
16 touches
28 conflicts
0x161e1ca1…0fd7
0x34b655…2a6f
14 touches
21 conflicts
0xf853eb8e…4027
0x34b655…2a6f
14 touches
21 conflicts
0xd49762c9…1359
0x34b655…2a6f
12 touches
15 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
10 touches
10 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: 0xab35264b…1cfa38
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity