pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,803,895
40 transactions · 34 stateful · 2026-05-15 18:18:26 UTC
Parallelism
73/100
Blocked
74%
Avg conflicts / tx
2.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,803,895 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w19w723w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc363a7ac…f343
0xd32edf…ff58
21 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0x3af0dd8e…0023
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 0xc363a7acde…b8f343
Audit this contract →
← previous block·next block →recent activity