pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,649,593
59 transactions · 41 stateful · 2026-05-10 09:48:29 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.81
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,649,593 · 59 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w310w013w114w015w116w217w318w424w228w333w441w542w643w744w846w947w1052w1153w1257w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22d7bbbc…c7e9
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
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
78 conflicts on slot 0x22d7bbbc18…d8c7e9
Audit this contract →
← previous block·next block →recent activity