pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,240
61 transactions · 46 stateful · 2026-05-15 14:00:07 UTC
Parallelism
77/100
Blocked
72%
Avg conflicts / tx
2.3
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,765,240 · 61 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w923w1024w1125w1226w1334w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e5f7239…417c
0xd32edf…ff58
21 touches
55 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xba5743c7…21c1
0x1b6862…e19c
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 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
55 conflicts on slot 0x2e5f7239e1…da417c
Audit this contract →
← previous block·next block →recent activity