pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,252
46 transactions · 30 stateful · 2026-05-15 14:00:12 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,765,252 · 46 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w212w214w015w116w227w028w129w230w331w432w533w638w341w743w844w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
18 touches
36 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0xedb848fe…6534
0x34b655…2a6f
14 touches
21 conflicts
0x9be2b99a…a959
0x34b655…2a6f
12 touches
15 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x57de3828…3fbb
0x34b655…2a6f
12 touches
15 conflicts
0x61ad45b1…15ac
0x34b655…2a6f
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: 0x34b6552d…112a6f
36 conflicts on slot 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity