pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,351,922
49 transactions · 34 stateful · 2026-05-13 15:58:36 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.47
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,351,922 · 49 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
1w02w03w09w010w115w216w319w322w223w225w426w127w232w433w537w638w739w840w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6e72cef…dd27
0xd32edf…ff58
19 touches
45 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x91ecc547…33ec
0x1b6862…e19c
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 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
45 conflicts on slot 0xa6e72cef60…63dd27
Audit this contract →
← previous block·next block →recent activity