pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,484,546
50 transactions · 39 stateful · 2026-05-14 06:41:23 UTC
Parallelism
78/100
Blocked
72%
Avg conflicts / tx
1.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,484,546 · 50 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
2w03w14w15w27w212w213w317w318w419w521w622w723w833w334w435w536w637w739w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a0465b8…ea9a
0xd32edf…ff58
15 touches
28 conflicts
0xf3981be5…2c47
0x34b655…2a6f
12 touches
15 conflicts
0xffe431af…8faa
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
10 touches
10 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 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
28 conflicts on slot 0x7a0465b88d…faea9a
Audit this contract →
← previous block·next block →recent activity