pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,382,821
44 transactions · 32 stateful · 2026-05-13 19:24:17 UTC
Parallelism
73/100
Blocked
63%
Avg conflicts / tx
1.27
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,382,821 · 44 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
1w02w13w24w36w08w111w015w121w022w123w224w325w426w537w341w943w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x8902ba1f…f4b6
0x34b655…2a6f
8 touches
6 conflicts
0xcef028ea…0df0
0xd32edf…ff58
7 touches
6 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x5d32a251…d929
0x34b655…2a6f
6 touches
3 conflicts
0x4e20d66f…4cdf
0x34b655…2a6f
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: 0x34b6552d…112a6f
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity