pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,328,463
39 transactions · 29 stateful · 2026-05-08 22:10:04 UTC
Parallelism
54/100
Blocked
62%
Avg conflicts / tx
4.03
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,328,463 · 39 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
1w02w13w24w35w46w57w68w710w811w912w1013w1114w1215w1316w1426w1527w1630w1738w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1656388…2382
0xd32edf…ff58
35 touches
153 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x46cb45de…a566
0x188d58…ea8e
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c4
0x1b6862…e19c
10 touches
10 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
153 conflicts on slot 0xf165638847…d62382
Audit this contract →
← previous block·next block →recent activity