pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,808,499
44 transactions · 30 stateful · 2026-05-11 03:40:12 UTC
Parallelism
57/100
Blocked
70%
Avg conflicts / tx
4
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #73,808,499 · 44 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1123w128w1229w1335w1436w1537w1638w1739w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50ef5ada…43c4
0xd32edf…ff58
37 touches
171 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0xc2aacf41…5504
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
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: 0xd32edf66…9fff58
171 conflicts on slot 0x50ef5ada47…dc43c4
Audit this contract →
← previous block·next block →recent activity