pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,892,144
59 transactions · 46 stateful · 2026-04-27 15:34:34 UTC
Parallelism
75/100
Blocked
70%
Avg conflicts / tx
2.27
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #70,892,144 · 59 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w012w113w215w317w118w619w248w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x7b7bcac3…8fbf
0x34b655…2a6f
16 touches
28 conflicts
0x1c913164…5c2e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x0520da1d…c88e
0x34b655…2a6f
12 touches
15 conflicts
0x3254d19b…f714
0x34b655…2a6f
12 touches
15 conflicts
0x414e9446…4b59
0x34b655…2a6f
12 touches
15 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity