pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,284,615
48 transactions · 36 stateful · 2026-05-04 02:17:49 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.54
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,284,615 · 48 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
1w02w14w05w08w014w115w116w220w021w122w223w324w425w526w627w728w229w332w134w136w237w338w139w246w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x88915805…fbc9
0x34b655…2a6f
8 touches
6 conflicts
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
8 touches
6 conflicts
0x4e02e30f…467f
0xd32edf…ff58
7 touches
6 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
28 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity