pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,046
50 transactions · 42 stateful · 2026-05-16 07:13:05 UTC
Parallelism
76/100
Blocked
74%
Avg conflicts / tx
2.74
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,920,046 · 50 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1017w818w919w1023w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ca2e971…e7a8
0xd32edf…ff58
23 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0xebd2f809…3132
0x34b655…2a6f
12 touches
15 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
12 touches
15 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0xeb0915f1…c150
0x34b655…2a6f
12 touches
15 conflicts
0xafd59af5…5257
0xc8689a…ee79
12 touches
15 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
66 conflicts on slot 0x3ca2e97115…c1e7a8
Audit this contract →
← previous block·next block →recent activity