pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,911,001
48 transactions · 34 stateful · 2026-04-27 17:40:10 UTC
Parallelism
79/100
Blocked
62%
Avg conflicts / tx
1.56
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #70,911,001 · 48 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
1w02w113w014w118w019w120w222w023w127w228w330w431w533w234w335w636w741w342w443w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
18 touches
36 conflicts
0x24968e6d…0132
0x065c9d…c394
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x131a2e…0da9
8 touches
6 conflicts
0xb9d2cf20…a668
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: 0x2a68ba18…8e90c5
36 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity