pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,238
37 transactions · 25 stateful · 2026-05-18 21:23:10 UTC
Parallelism
57/100
Blocked
76%
Avg conflicts / tx
3.46
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #75,478,238 · 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
1w02w13w24w35w46w57w68w79w811w112w213w219w920w1021w1123w1224w1325w1426w1532w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8766d542…0dca
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…0000
0x094452…0a09
6 touches
3 conflicts
0x00000000…0002
0x094452…0a09
6 touches
3 conflicts
0x00000000…0004
0x094452…0a09
6 touches
3 conflicts
0x62e20208…be65
0x0555e3…2b9c
6 touches
3 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
6 touches
3 conflicts
0xe75ce681…ba60
0x188d58…ea8e
6 touches
3 conflicts
0x9e223b01…38b2
0x3bd359…433a
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
120 conflicts on slot 0x8766d54283…070dca
Audit this contract →
← previous block·next block →recent activity