pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,453
47 transactions · 35 stateful · 2026-05-16 07:15:48 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,920,453 · 47 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w010w011w114w016w117w118w121w022w127w028w129w230w331w132w233w334w435w536w638w639w243w444w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06d6914…74d9
0xd32edf…ff58
13 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
8 touches
6 conflicts
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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
21 conflicts on slot 0xf06d691488…7374d9
Audit this contract →
← previous block·next block →recent activity