pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,998,722
← previous block
next block →
recent activity
Analyzing
Block #70,998,722
13 transactions · 9 stateful · 2026-04-28 03:24:24 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,998,722
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeem
#2
0x572c8ce3
#3
forward
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#7
forward
#8
0x69f028e0
#9
0x69f028e0
#10
setData
#11
updatePrices
#12
updatePrices
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x526febd7…86ac
0x065c9d…c394
4 touches
1 conflict
0x81086d93…6a19
0x065c9d…c394
4 touches
1 conflict
0x8d44d1e7…4f0e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x03d109e4…5f1f
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity