pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,429,517
46 transactions · 36 stateful · 2026-05-04 18:23:52 UTC
Parallelism
76/100
Blocked
69%
Avg conflicts / tx
1.76
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #72,429,517 · 46 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w09w111w113w214w119w321w022w123w224w335w238w139w340w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1fd24a0…eaa6
0x34b655…2a6f
18 touches
36 conflicts
0x2484cc15…5afc
0x34b655…2a6f
14 touches
21 conflicts
0xafd59af5…5257
0xc8689a…ee79
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x6423fcab…a7c1
0x34b655…2a6f
9 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: 0x34b6552d…112a6f
36 conflicts on slot 0xe1fd24a00e…feeaa6
Audit this contract →
← previous block·next block →recent activity