pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,630,394
63 transactions · 49 stateful · 2026-05-14 23:00:01 UTC
Parallelism
64/100
Blocked
80%
Avg conflicts / tx
3.3
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #74,630,394 · 63 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w28w313w414w016w117w218w319w420w521w622w752w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xafd59af5…5257
0xc8689a…ee79
12 touches
15 conflicts
0x0cb5b886…beee
0x34b655…2a6f
12 touches
15 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity