pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,762,022
58 transactions · 42 stateful · 2026-05-15 13:38:36 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
2.91
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,762,022 · 58 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w614w244w745w848w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
26 touches
78 conflicts
0x5553f577…f9ee
0x34b655…2a6f
18 touches
36 conflicts
0xdd62af69…9ab1
0xd32edf…ff58
17 touches
36 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
14 touches
21 conflicts
0xeb0915f1…c150
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xafd59af5…5257
0xc8689a…ee79
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
78 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity