pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,374,963
32 transactions · 28 stateful · 2026-05-09 03:19:18 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
2.84
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,374,963 · 32 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w811w912w1014w1116w817w919w1022w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de47518…3bcd
0xd32edf…ff58
23 touches
66 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0xbba89d28…a968
0x065c9d…c394
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0013
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
66 conflicts on slot 0x5de475180b…c83bcd
Audit this contract →
← previous block·next block →recent activity