pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,094,764
← previous block
next block →
recent activity
Analyzing
Block #71,094,764
11 transactions · 10 stateful · 2026-04-28 14:03:55 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,094,764
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 2
#6
setData
#7
0x0c7abd22
#9
updateMetadata
#10
approve
#5
0x6463ffd1
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x764d084b…67f4
0x065c9d…c394
4 touches
1 conflict
0xe8978f81…d2b9
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x9660ee3c…8f52
0x065c9d…c394
3 touches
1 conflict
0xde07c6ca…2212
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity