pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,092,601
55 transactions · 36 stateful · 2026-04-28 13:49:31 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1.18
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #71,092,601 · 55 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
1w02w13w25w36w47w58w69w710w811w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2b40d6…287c
0xd32edf…ff58
21 touches
55 conflicts
0xfac61869…a55b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 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: 0xd32edf66…9fff58
55 conflicts on slot 0x5d2b40d664…d7287c
Audit this contract →
← previous block·next block →recent activity