pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,233,768
87 transactions · 54 stateful · 2026-05-03 20:36:05 UTC
Parallelism
77/100
Blocked
78%
Avg conflicts / tx
2.32
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #72,233,768 · 87 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w312w564w565w666w770w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0x08b492a7…7f8d
0xd32edf…ff58
15 touches
28 conflicts
0x1c389468…6b0e
0x34b655…2a6f
12 touches
15 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
12 touches
15 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x9be2b99a…a959
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity