pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,393,830
37 transactions · 29 stateful · 2026-05-09 05:24:49 UTC
Parallelism
51/100
Blocked
66%
Avg conflicts / tx
3.05
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,393,830 · 37 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
1w02w13w24w35w46w57w68w79w815w816w917w1023w1124w1225w1326w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88aa26e4…53dc
0xd32edf…ff58
27 touches
91 conflicts
0x22e295f5…1bef
0x065c9d…c394
12 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
12 touches
15 conflicts
0x794b8f81…3ead
0x1b6862…e19c
12 touches
15 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
91 conflicts on slot 0x88aa26e44a…f753dc
Audit this contract →
← previous block·next block →recent activity