pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,923,032
51 transactions · 39 stateful · 2026-04-27 19:00:16 UTC
Parallelism
76/100
Blocked
62%
Avg conflicts / tx
1.41
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #70,923,032 · 51 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w418w121w022w123w224w327w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x8d918c20…7da0
0xd32edf…ff58
11 touches
15 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x6aa624fd…a850
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x3b3a5945…10d0
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity