pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,095,688
61 transactions · 43 stateful · 2026-04-28 14:10:06 UTC
Parallelism
72/100
Blocked
67%
Avg conflicts / tx
2.16
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #71,095,688 · 61 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w010w113w116w217w318w319w420w544w347w648w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x801a6e57…d85c
0x34b655…2a6f
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x62d6e82b…a750
0x34b655…2a6f
10 touches
10 conflicts
0x8aa1941d…2988
0x34b655…2a6f
10 touches
10 conflicts
0x904fc3c0…00ec
0x34b655…2a6f
10 touches
10 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity