pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,060
61 transactions · 47 stateful · 2026-05-04 02:41:01 UTC
Parallelism
69/100
Blocked
85%
Avg conflicts / tx
3.79
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #72,288,060 · 61 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
1w02w13w24w35w46w57w68w519w620w721w824w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
32 touches
120 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x629e09e5…692a
0x34b655…2a6f
16 touches
28 conflicts
0x672a5835…6cf0
0xd32edf…ff58
15 touches
28 conflicts
0x893cd52c…5766
0x34b655…2a6f
12 touches
15 conflicts
0xaf498679…7732
0x34b655…2a6f
12 touches
15 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
12 touches
15 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
120 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity