pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,679,353
45 transactions · 29 stateful · 2026-05-10 13:09:16 UTC
Parallelism
64/100
Blocked
76%
Avg conflicts / tx
2.93
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,679,353 · 45 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1320w1331w1433w1539w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd4360e9…a5f7
0xd32edf…ff58
31 touches
120 conflicts
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a05
0x1b6862…e19c
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
120 conflicts on slot 0xcd4360e971…11a5f7
Audit this contract →
← previous block·next block →recent activity