pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,498,717
46 transactions · 36 stateful · 2026-05-05 02:04:43 UTC
Parallelism
72/100
Blocked
72%
Avg conflicts / tx
2.5
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #72,498,717 · 46 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w111w012w113w214w315w416w517w618w730w231w332w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0x7e9d3a…9fda
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xec1d6663…6042
0x34b655…2a6f
14 touches
21 conflicts
0x8571fbdb…345a
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd086307a…badd
0xd32edf…ff58
9 touches
10 conflicts
0x7cb2f3fa…4836
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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity