pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,479,182
64 transactions · 36 stateful · 2026-05-18 21:29:38 UTC
Parallelism
75/100
Blocked
61%
Avg conflicts / tx
1.97
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #75,479,182 · 64 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
1w02w13w25w36w47w58w611w712w815w916w1017w1119w1022w248w1449w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c01c75e…1d35
0xd32edf…ff58
27 touches
91 conflicts
0x17606ba6…1b6e
0x754704…b603
18 touches
36 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
10 touches
10 conflicts
0x5dfa485c…cf52
0x754704…b603
10 touches
10 conflicts
0x00000000…0000
0x9b60e5…f8ac
10 touches
10 conflicts
0x00000000…0004
0x9b60e5…f8ac
10 touches
10 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
10 touches
10 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 0x0c01c75e26…dc1d35
Audit this contract →
← previous block·next block →recent activity