pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,352,190
66 transactions · 46 stateful · 2026-05-13 16:00:23 UTC
Parallelism
71/100
Blocked
80%
Avg conflicts / tx
2.98
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,352,190 · 66 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1215w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03214f2b…6659
0xd32edf…ff58
25 touches
78 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0019
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0x48a29a03…c436
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
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
78 conflicts on slot 0x03214f2bf3…9d6659
Audit this contract →
← previous block·next block →recent activity