pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,956,062
← previous block
next block →
recent activity
Analyzing
Block #70,956,062
10 transactions · 10 stateful · 2026-04-27 22:40:09 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,062
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x6463ffd1
· blocks 1
#3
redeemDelegations
#5
updateDataFeedsValuesPartial
#6
cashOut
#7
setData
#8
0x39435dac
· blocks 1
#4
0x6463ffd1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9eb8a8b…3025
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe04853fb…1040
0x065c9d…c394
4 touches
1 conflict
0xeaba4491…5d92
0x065c9d…c394
4 touches
1 conflict
0x208f5b43…2d29
0x065c9d…c394
3 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
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
0xa9eb8a8b09…b03025
Audit this contract →
← previous block
·
next block →
recent activity