pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,846,432
← previous block
next block →
recent activity
Analyzing
Block #70,846,432
9 transactions · 7 stateful · 2026-04-27 10:30:08 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,846,432
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeemDelegations
#2
updateDataFeedsValuesPartial
#3
execute
#4
0x6463ffd1
· blocks 1
#6
collect
#7
0x69ef3b28
#8
setData
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x531131c5…be9f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x81128d71…7888
0x065c9d…c394
4 touches
1 conflict
0x57993c58…b448
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13e81263…6058
0x065c9d…c394
4 touches
1 conflict
0x16ee19a6…7a81
0x065c9d…c394
4 touches
1 conflict
0x5e391f61…848b
0x065c9d…c394
2 touches
1 conflict
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
0x531131c5bb…b6be9f
Audit this contract →
← previous block
·
next block →
recent activity