pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,043,102
53 transactions · 34 stateful · 2026-05-07 14:31:24 UTC
Parallelism
81/100
Blocked
68%
Avg conflicts / tx
1.53
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,043,102 · 53 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w012w013w114w221w322w225w327w428w539w640w741w743w750w852w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb018a5b0…f57a
0xd32edf…ff58
17 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
10 touches
10 conflicts
0x005fb969…2d97
0x34b655…2a6f
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x2877f440…c2c8
0x34b655…2a6f
8 touches
6 conflicts
0x3702b140…97ea
0x34b655…2a6f
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
36 conflicts on slot 0xb018a5b0f1…c0f57a
Audit this contract →
← previous block·next block →recent activity