pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,934
57 transactions · 33 stateful · 2026-05-10 11:04:50 UTC
Parallelism
65/100
Blocked
79%
Avg conflicts / tx
3.68
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #73,660,934 · 57 txs across 20 waves · depth 20
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
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w812w913w1014w1115w1216w1317w1429w131w1237w1538w1642w1743w1844w1945w1356w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c43491a…6e73
0xd32edf…ff58
39 touches
190 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x6aa624fd…a84f
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
190 conflicts on slot 0x1c43491a24…906e73
Audit this contract →
← previous block·next block →recent activity