pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,694,791
64 transactions · 44 stateful · 2026-05-10 14:53:20 UTC
Parallelism
72/100
Blocked
75%
Avg conflicts / tx
2.28
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,694,791 · 64 txs across 18 waves · depth 18
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
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w313w417w536w248w549w650w751w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x4545f3ab…a5c3
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002c
0x1b6862…e19c
14 touches
21 conflicts
0x4423a307…9f46
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity