pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,493,123
42 transactions · 36 stateful · 2026-05-09 16:25:37 UTC
Parallelism
60/100
Blocked
72%
Avg conflicts / tx
2.02
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #73,493,123 · 42 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w28w39w411w619w724w825w926w1027w1128w1229w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3794dea3…c694
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd18a8dca…4529
0x1b6862…e19c
10 touches
10 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
10 touches
10 conflicts
0x00000000…0013
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
28 conflicts on slot 0x3794dea369…dcc694
Audit this contract →
← previous block·next block →recent activity