pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,075
43 transactions · 29 stateful · 2026-05-15 13:59:01 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
1.56
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,765,075 · 43 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w38w29w016w121w022w123w224w325w426w527w628w729w837w938w1039w1140w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
8 touches
6 conflicts
0x36cdae67…8407
0x34b655…2a6f
8 touches
6 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
8 touches
6 conflicts
0xa7165de2…e67b
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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity