pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,917,771
50 transactions · 41 stateful · 2026-04-27 18:25:18 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.34
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #70,917,771 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w29w011w112w013w014w015w117w018w119w220w321w422w523w525w626w731w233w137w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
10 touches
10 conflicts
0xc0bfaa75…e24f
0xd32edf…ff58
9 touches
10 conflicts
0x6f2e60dc…e661
0x34b655…2a6f
8 touches
6 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
8 touches
6 conflicts
0x85566ff3…565d
0x34b655…2a6f
8 touches
6 conflicts
0x87a380d9…2d04
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity