pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,645,992
62 transactions · 41 stateful · 2026-05-15 00:43:55 UTC
Parallelism
87/100
Blocked
71%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,645,992 · 62 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w113w216w221w322w423w526w227w429w331w543w751w355w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5e111a2…4b2b
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
12 touches
15 conflicts
0x060add69…d78b
0x188d58…ea8e
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x01e7b865…6e70
0x188d58…ea8e
8 touches
6 conflicts
0x060add69…d78c
0x188d58…ea8e
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 0xe5e111a275…ef4b2b
Audit this contract →
← previous block·next block →recent activity