pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,304,596
42 transactions · 36 stateful · 2026-05-13 10:43:56 UTC
Parallelism
67/100
Blocked
86%
Avg conflicts / tx
3.31
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,304,596 · 42 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w111w212w324w425w526w628w731w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x7ef155a8…2855
0xd32edf…ff58
17 touches
36 conflicts
0x7f38bfbc…61e3
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0028
0x1b6862…e19c
12 touches
15 conflicts
0x17a7f697…dcb1
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity