pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,741,441
53 transactions · 39 stateful · 2026-05-01 13:54:20 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.55
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #71,741,441 · 53 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
1w02w13w25w37w48w016w517w018w123w127w028w129w230w331w435w645w546w648w851w1152w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x1bc9b1ca…85ef
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x0277d8de…caf4
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xb87ecd0c…6219
0x34b655…2a6f
8 touches
6 conflicts
0x2202504e…fad0
0x34b655…2a6f
8 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity