pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,415,424
39 transactions · 34 stateful · 2026-05-13 23:01:18 UTC
Parallelism
67/100
Blocked
82%
Avg conflicts / tx
2.95
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,415,424 · 39 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
1w02w13w24w35w16w07w19w211w012w113w214w315w416w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
20 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0x46356904…5ead
0x34b655…2a6f
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa3c1ee41…bdef
0xd32edf…ff58
7 touches
6 conflicts
0x014e90b3…470f
0x34b655…2a6f
6 touches
3 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: 0xab35264b…1cfa38
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity