pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,353,220
47 transactions · 39 stateful · 2026-05-13 16:07:15 UTC
Parallelism
66/100
Blocked
74%
Avg conflicts / tx
2.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #74,353,220 · 47 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w19w211w113w215w016w017w118w219w320w433w334w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
12 touches
15 conflicts
0x6820b91b…43f9
0xd32edf…ff58
11 touches
15 conflicts
0x99f080dc…58c1
0x34b655…2a6f
10 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity