pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,092,203
58 transactions · 40 stateful · 2026-04-28 13:46:52 UTC
Parallelism
83/100
Blocked
65%
Avg conflicts / tx
1.45
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #71,092,203 · 58 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
1w02w13w05w06w18w19w111w013w232w237w241w642w744w846w347w448w549w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816b57f5…3020
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x42102e63…8aa4
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0x816b57f529…613020
Audit this contract →
← previous block·next block →recent activity