pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,032,631
55 transactions · 32 stateful · 2026-05-16 19:46:22 UTC
Parallelism
69/100
Blocked
75%
Avg conflicts / tx
2.18
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #75,032,631 · 55 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1131w1232w1334w1242w1445w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2b9ba4…b135
0xd32edf…ff58
27 touches
91 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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 0x0d2b9ba42b…feb135
Audit this contract →
← previous block·next block →recent activity