pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,430
43 transactions · 33 stateful · 2026-05-04 15:03:25 UTC
Parallelism
72/100
Blocked
76%
Avg conflicts / tx
2.12
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,399,430 · 43 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w29w311w113w014w116w220w021w122w223w324w425w526w628w329w430w232w434w235w537w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x8571fbdb…345a
0x34b655…2a6f
12 touches
15 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xf05a38f9…0fac
0xd32edf…ff58
9 touches
10 conflicts
0x12bc0d2c…1c12
0x34b655…2a6f
8 touches
6 conflicts
0x220f4f84…15f8
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity