pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,026,834
46 transactions · 35 stateful · 2026-05-07 12:43:05 UTC
Parallelism
63/100
Blocked
69%
Avg conflicts / tx
3.11
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #73,026,834 · 46 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1218w119w1321w122w1423w1525w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9bd454…e37d
0xd32edf…ff58
31 touches
120 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x70b2f813…783c
0x2a68ba…90c5
8 touches
6 conflicts
0xb389d45f…8a4c
0x34b655…2a6f
8 touches
6 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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: 0xd32edf66…9fff58
120 conflicts on slot 0xde9bd454e6…58e37d
Audit this contract →
← previous block·next block →recent activity