pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,555,802
79 transactions · 56 stateful · 2026-05-14 14:40:20 UTC
Parallelism
77/100
Blocked
71%
Avg conflicts / tx
2.29
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #74,555,802 · 79 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w323w425w526w627w728w853w854w955w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e8170a…ee4a
0xd32edf…ff58
21 touches
55 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x17606ba6…1b6e
0x754704…b603
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002e
0x1b6862…e19c
14 touches
21 conflicts
0x93afca4c…b47e
0x1b6862…e19c
14 touches
21 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: 0xd32edf66…9fff58
55 conflicts on slot 0xf9e8170aeb…0eee4a
Audit this contract →
← previous block·next block →recent activity