pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,560,713
← previous block
next block →
recent activity
Analyzing
Block #71,560,713
12 transactions · 10 stateful · 2026-04-30 17:51:19 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,560,713
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
commitVerification
#3
0x98c01e2a
#4
0x55e58ed0
#6
0xeffdedb0
#7
updateDataFeedsValuesPartial
#8
setData
#9
updateTemporalNumericValuesV1
#10
0x39435dac
#11
0x39435dac
#5
0xf2acfec3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x6b000777…7040
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x97f9a4b1…b9ad
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0007
0x09f880…ede0
2 touches
0 conflicts
0x00000000…000a
0x09f880…ede0
2 touches
0 conflicts
0x00000000…0004
0x1571e3…513f
2 touches
0 conflicts
0xbb6daa0c…9f5f
0x1571e3…513f
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
0x348fda08cf…fc7e96
Audit this contract →
← previous block
·
next block →
recent activity