pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,555,747
49 transactions · 31 stateful · 2026-05-14 14:39:58 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.84
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,555,747 · 49 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
1w02w13w25w07w08w112w017w124w026w127w228w329w430w538w143w244w645w747w948w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0x5c074a38…c1d3
0x34b655…2a6f
6 touches
3 conflicts
0xd5b4a8ba…6908
0xd32edf…ff58
5 touches
3 conflicts
0x4979282b…2937
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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: 0x34b6552d…112a6f
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity