pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,605,900
59 transactions · 48 stateful · 2026-05-14 20:16:42 UTC
Parallelism
70/100
Blocked
81%
Avg conflicts / tx
3.15
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #74,605,900 · 59 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w48w09w113w114w215w523w227w345w551w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
32 touches
120 conflicts
0xacd10bf4…2244
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0xedb848fe…6534
0x34b655…2a6f
14 touches
21 conflicts
0x57de3828…3fbb
0x34b655…2a6f
14 touches
21 conflicts
0x0711ec2d…d973
0x34b655…2a6f
14 touches
21 conflicts
0xd49762c9…1359
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 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
120 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity