pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,926,043
31 transactions · 30 stateful · 2026-05-11 16:43:11 UTC
Parallelism
61/100
Blocked
67%
Avg conflicts / tx
2.87
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,926,043 · 31 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w49w010w111w212w313w414w515w616w717w820w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xc6417de0…2191
0xc8689a…ee79
22 touches
55 conflicts
0xac8e97a0…8426
0x34b655…2a6f
22 touches
55 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
22 touches
55 conflicts
0x4f483049…3cc7
0x34b655…2a6f
22 touches
55 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
22 touches
55 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
22 touches
55 conflicts
0xd49762c9…1359
0x34b655…2a6f
18 touches
36 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: 0x34b6552d…112a6f
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity