pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,343,782
37 transactions · 28 stateful · 2026-05-08 23:51:52 UTC
Parallelism
57/100
Blocked
71%
Avg conflicts / tx
3.81
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,343,782 · 37 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1116w1219w1428w1329w1433w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c50d4dc…50ff
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0xdbc6e634…e16a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 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
120 conflicts on slot 0x5c50d4dc77…5a50ff
Audit this contract →
← previous block·next block →recent activity