pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,515,865
40 transactions · 34 stateful · 2026-05-14 10:10:59 UTC
Parallelism
57/100
Blocked
71%
Avg conflicts / tx
2.6
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,515,865 · 40 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
1w02w13w24w38w09w110w211w012w113w214w315w416w517w618w719w820w924w325w334w1139w16
- 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
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x58e06bab…34d0
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x20ac0567…c954
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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity