pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,224,618
67 transactions · 55 stateful · 2026-05-03 19:34:34 UTC
Parallelism
73/100
Blocked
75%
Avg conflicts / tx
3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #72,224,618 · 67 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w09w210w313w115w316w417w518w646w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0x7e9d3a…9fda
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x7ee110ef…8394
0x34b655…2a6f
12 touches
15 conflicts
0xb1856468…e84f
0x34b655…2a6f
12 touches
15 conflicts
0xafd59af5…5257
0xc8689a…ee79
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity