pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,047
75 transactions · 51 stateful · 2026-05-04 02:40:56 UTC
Parallelism
77/100
Blocked
78%
Avg conflicts / tx
3.12
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #72,288,047 · 75 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w69w710w811w936w1037w1139w1259w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0x3e4fbf3d…3594
0xd32edf…ff58
25 touches
78 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xbb975a6c…bff4
0x34b655…2a6f
16 touches
28 conflicts
0x893cd52c…5766
0x34b655…2a6f
14 touches
21 conflicts
0x2484cc15…5afc
0x34b655…2a6f
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
14 touches
21 conflicts
0xaf498679…7732
0x34b655…2a6f
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
91 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity