pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,762,941
72 transactions · 48 stateful · 2026-05-15 13:44:46 UTC
Parallelism
82/100
Blocked
69%
Avg conflicts / tx
1.92
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,762,941 · 72 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
1w02w13w24w35w46w57w28w012w120w021w357w159w360w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x87431245…a6b7
0xd32edf…ff58
11 touches
15 conflicts
0xb9868b52…c77f
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 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
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity