pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,908,495
80 transactions · 70 stateful · 2026-04-27 17:23:29 UTC
Parallelism
75/100
Blocked
79%
Avg conflicts / tx
3.26
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #70,908,495 · 80 txs across 20 waves · depth 20
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
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w012w113w014w116w220w321w422w423w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
26 touches
78 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xe6bc2705…d15b
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xcfb9c304…2097
0xd32edf…ff58
11 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: 0xb857c13a…1a9be1
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity