pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,479,172
58 transactions · 27 stateful · 2026-05-18 21:29:34 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
1.97
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #75,479,172 · 58 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w410w512w614w715w816w917w1018w1119w1246w1347w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bd1237d…2313
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x3af0dd8e…0021
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
105 conflicts on slot 0x5bd1237d66…f12313
Audit this contract →
← previous block·next block →recent activity