pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,922,851
← previous block
next block →
recent activity
Analyzing
Block #70,922,851
11 transactions · 9 stateful · 2026-04-27 18:59:05 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,922,851
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1d8a46f1…0d66
0x065c9d…c394
4 touches
1 conflict
0x61703ff2…cead
0x065c9d…c394
4 touches
1 conflict
0x6ae53523…2c70
0x065c9d…c394
4 touches
1 conflict
0xbc8d26b8…b6ca
0x065c9d…c394
4 touches
1 conflict
0xc1f435e6…5c53
0x065c9d…c394
4 touches
1 conflict
0xe2e8270d…7d70
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity