pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,331,488
74 transactions · 40 stateful · 2026-05-13 13:42:47 UTC
Parallelism
84/100
Blocked
68%
Avg conflicts / tx
1.31
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,331,488 · 74 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w18w111w013w214w219w120w224w328w351w452w553w654w755w857w965w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd3a12b5…1a6e
0xd32edf…ff58
19 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xffe431af…8faa
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc1f28224…cb43
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: 0xd32edf66…9fff58
45 conflicts on slot 0xbd3a12b5cd…fa1a6e
Audit this contract →
← previous block·next block →recent activity