pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,328,206
43 transactions · 30 stateful · 2026-05-08 22:08:22 UTC
Parallelism
65/100
Blocked
73%
Avg conflicts / tx
3.05
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,328,206 · 43 txs across 15 waves · depth 15
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
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w010w113w314w115w219w421w322w423w524w626w727w828w933w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf7f31e9…9150
0xd32edf…ff58
29 touches
105 conflicts
0x56a919c4…ab49
0xee8c0e…1242
14 touches
21 conflicts
0x729c91b8…9537
0x188d58…ea8e
10 touches
10 conflicts
0x729c91b8…9539
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x9ea57326…329f
0x34b655…2a6f
4 touches
1 conflict
0xa980598e…ec52
0x3bd359…433a
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: 0xd32edf66…9fff58
105 conflicts on slot 0xcf7f31e92d…0a9150
Audit this contract →
← previous block·next block →recent activity