pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,763,958
45 transactions · 34 stateful · 2026-05-15 13:51:31 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
2.78
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #74,763,958 · 45 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w010w114w215w017w121w022w123w224w325w426w527w628w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
30 touches
105 conflicts
0xc6417de0…2191
0xc8689a…ee79
18 touches
36 conflicts
0x9be2b99a…a959
0x34b655…2a6f
18 touches
36 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
18 touches
36 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
18 touches
36 conflicts
0x5aeaf08b…cbf7
0x34b655…2a6f
18 touches
36 conflicts
0x32ee90db…decc
0x34b655…2a6f
18 touches
36 conflicts
0x388e001a…7e04
0x34b655…2a6f
16 touches
28 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
105 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity