pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,460
55 transactions · 30 stateful · 2026-05-10 10:00:59 UTC
Parallelism
67/100
Blocked
77%
Avg conflicts / tx
2.95
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,651,460 · 55 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1340w1441w1542w1652w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc66d587…f56f
0xd32edf…ff58
35 touches
153 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x03f9cc30…b468
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
153 conflicts on slot 0xcc66d587e9…9ef56f
Audit this contract →
← previous block·next block →recent activity