pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,860,119
62 transactions · 49 stateful · 2026-05-06 18:13:31 UTC
Parallelism
68/100
Blocked
80%
Avg conflicts / tx
3.65
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #72,860,119 · 62 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
1w02w13w24w35w46w57w38w411w116w422w624w525w626w727w861w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x17606ba6…1b6e
0x754704…b603
18 touches
36 conflicts
0xe70f6c1d…2539
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x736c5b69…fb3f
0x34b655…2a6f
14 touches
21 conflicts
0xafdd9f0b…c228
0xd32edf…ff58
13 touches
21 conflicts
0x664bf99e…0a8c
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity