pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,856,135
51 transactions · 40 stateful · 2026-05-06 17:47:00 UTC
Parallelism
61/100
Blocked
80%
Avg conflicts / tx
3.02
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #72,856,135 · 51 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
1w02w13w24w35w46w510w411w512w416w550w6
- 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
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
12 touches
15 conflicts
0x17a7f697…dcb5
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x5717771c…45ed
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity