pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,502,577
54 transactions · 36 stateful · 2026-05-14 08:41:30 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,502,577 · 54 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w118w222w024w025w128w030w131w232w333w434w235w537w639w746w847w949w150w251w352w453w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee43b798…6bfe
0xd32edf…ff58
19 touches
45 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xee43b79868…306bfe
Audit this contract →
← previous block·next block →recent activity