pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,328,205
42 transactions · 28 stateful · 2026-05-08 22:08:22 UTC
Parallelism
55/100
Blocked
82%
Avg conflicts / tx
4.31
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #73,328,205 · 42 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
1w02w13w24w35w46w57w68w710w811w912w1013w1114w1223w1227w1328w1429w1530w1631w1733w1834w1341w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd767e576…4a09
0xd32edf…ff58
37 touches
171 conflicts
0x6f08361d…bda6
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
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…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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
171 conflicts on slot 0xd767e57637…c24a09
Audit this contract →
← previous block·next block →recent activity